Latest revision as of 06:28, 12 March 2025

.seigr File Format

The .seigr file (pronounced "dot-seigr") is the Symbiotic Environment of Interconnected Generative Records, forming the fundamental unit of structured, ethical, and adaptive data within the Seigr Ecosystem.

Each .seigr file encapsulates Seigr Cells, modular information units with a genetic-like data lineage, resilient replication, and self-healing properties. Through RE-L (Rebel Earthling License), every .seigr file inherits, enforces, and propagates ethical licensing at both the file and Seigr Cell levels.

This format is the foundation of the Seigr Protocol, ensuring that data remains decentralized, cryptographically verified, and ethically managed across the network.

Concept and Structure

The .seigr format combines biological principles, cryptographic hashing, and modular design to form an interconnected, evolving data ecosystem.

Capsule-Based Execution

Each .seigr file functions as a Seigr Capsule, operating within the Capsule Execution Layer (SCE). This ensures:

Immutable Capsule Integrity → Each .seigr file maintains self-contained execution logic, ensuring data lineage and cryptographic trust.
Multi-Path Hash Linking → Capsules interlink using primary and secondary hashes, ensuring resilience and non-linear data retrieval.

Seigr Cell Inheritance & RE-L Integration

Every .seigr file is composed of Seigr Cells—discrete, interlinked data units.
RE-L enforcement occurs at the Cell level, ensuring that every contribution retains its licensing, origin, and ethical metadata.
Like DNA sequences in biological organisms, Seigr Cells pass licensing rules through cryptographic linkage, ensuring immutable lineage tracking.

Generative & Adaptive Data Structure

Evolutionary Storage Model → Like biological cells storing and transmitting genetic information, .seigr files adapt to evolving network conditions.
RE-L Genetic Print → Every .seigr file inherits ethical constraints encoded into its Seigr Cells, ensuring indelible contributor attribution.

Seigr Protocol & Cryptographic Structure

The Seigr Protocol governs .seigr file behavior through a structured, self-verifiable data and execution framework.

Core Components

Seigr Metadata → Ensures each Seigr Cell retains distinct, traceable, and interoperable records.
Temporal Layering → Embeds time-indexed snapshots, enabling historical reconstruction & rollback.
Encoder/Decoder Module → Converts binary data into senary (base-6) encoding for energy-efficient processing.

RE-L Licensing Enforcement

Every .seigr file contains an immutable RE-L enforcement layer, ensuring:

Contributor Attribution → Every Seigr Cell retains RE-L metadata, permissions, and monetization rules.
Multi-Layer Lineage Tracking → Changes are cryptographically logged, preventing data corruption or unauthorized alteration.

Mathematical Structure: Multi-Path Hashing

Each .seigr file maintains multi-dimensional hash linking, ensuring fault tolerance and adaptive retrieval.

Let:

H(c) be the hash of a Seigr Cell c.
H'(c, t) represent the cryptographic lineage of c at time t.

Multi-path hash linking ensures: $H'(c,t)=H(c)\oplus H(c_{parent})\oplus H(t)$

Where:

H(c_parent) ensures cryptographic inheritance.
H(t) timestamps lineage evolution.

Binary-Senary Hybrid Execution & Sensory Tagging

The .seigr format integrates Seigr-native processing with legacy binary execution, preserving data lineage and RE-L governance.

Hybrid Execution

UBSB allows seamless execution of binary processes inside Seigr Capsules.
Binary Payload Encapsulation ensures non-native data can still inherit Seigr’s ethical and security principles.

Sensory-Based Processing

Sensory Metadata Tagging → .seigr files attach sensory-executable metadata, enabling AI-driven retrieval and pattern recognition.
Capsule-Based Sensory Abstraction Layer (CBSAL) → Facilitates context-aware Seigr-native AI interactions.

Key Features of .seigr Files

The .seigr format incorporates advanced resilience, modularity, and cryptographic security.

Key Features of .seigr Files
Feature	Description
Fixed Size (53,194 Bytes)	Standardized data capsule size ensures predictable replication & efficient retrieval.
Senary Encoding	Base-6 encoding minimizes energy usage, aligning with Seigr’s eco-conscious computing principles.
Primary & Secondary Hash Links	Ensures multi-path retrieval, fault tolerance, and non-linear execution tracking.
Demand-Based Replication	Capsules replicate based on real-time access patterns, ensuring optimal resource allocation.
IPFS Compatibility	.seigr files integrate with IPFS for decentralized redundancy.

Adaptive Replication & Self-Healing

Biologically-Inspired Replication

Like neural networks adjusting synaptic strength, .seigr capsules replicate adaptively based on demand & access frequency.

Let:

A be the capsule access rate.
R be its redundancy factor.
S be its security classification.

The probability of replication follows: $P_{replicate}={\frac {A}{R+S}}$

Self-Healing & Integrity Enforcement

If corruption is detected:

Multi-Path Hash Recovery → Capsules rebuild from alternative hash references.
Dynamic Regeneration → Seigr Cells self-reconstruct by cross-verifying with parent nodes.

Node Identity & Trust-Based Execution

Each .seigr file is bound to Seigr's cryptographic identity model, ensuring trusted execution.

Node Identity & Trust-Based Execution
Security Feature	Description
Hardware-Bound Cryptographic Signatures	Prevents unauthorized execution outside verified Seigr nodes.
Network-Wide Trust Enforcement	Execution lineage tracking prevents unauthorized capsule replication.
Seigr Hardware Identity Layer (SHIL)	Automatically authenticates and validates all .seigr executions.

RE-L Genetic Print & Contribution Unit (CU) Tracking

Inherited RE-L Licensing at Every Level

Each Seigr Cell inside a .seigr file retains:

Immutable Contribution Units (CUs) that track creator attributions, role definitions, and licensing metadata.
Adaptive Contribution Units (ACUs) for layered modifications without altering core lineage.
RE-L Automated Enforcement → Unauthorized licensing changes trigger Hyphen Network validation.

Mathematically: $L_{inherit}=L_{parent}\oplus H(CU)\oplus H(ACU)$ where:

L_{inherit} is inherited licensing.
H(CU) enforces Contribution Unit rules.
H(ACU) tracks modifications.

Conclusion

The .seigr format redefines digital integrity through modular evolution, ethical governance, and cryptographic enforcement. Every .seigr file is a living, interwoven data entity, inheriting RE-L like genetic markers to ensure a sustainable, decentralized, and ethically governed future.

@@ Line 1: / Line 1: @@
 = .seigr File Format =
-The '''.seigr''' file (pronounced "dot-seigr") is an advanced data format developed for the [[Special:MyLanguage/Seigr Urcelial-net|Seigr Urcelial-net]], a decentralized network inspired by the adaptive, layered resilience of mycelial networks. The '''.seigr''' format facilitates secure, multi-dimensional data storage and retrieval across decentralized nodes, reimagining data management with embedded segmentation, self-referencing metadata, and re-assembly instructions. Each '''.seigr''' file is an interactive, evolving entity within a four-dimensional structure, enabling adaptive, time-aware retrieval and ongoing resilience within the network.
+The ''.seigr'' file ('''pronounced "dot-seigr"''') is the '''Symbiotic Environment of Interconnected Generative Records''', forming the fundamental unit of structured, ethical, and adaptive data within the '''Seigr Ecosystem'''.
-== Why the .seigr File Format? ==
+Each ''.seigr'' file '''encapsulates Seigr Cells''', modular information units with a '''genetic-like data lineage''', '''resilient replication''', and '''self-healing''' properties. Through '''RE-L (Rebel Earthling License)''', every ''.seigr'' file '''inherits, enforces, and propagates ethical licensing''' at both the '''file and Seigr Cell levels'''.
-As data decentralizes, storage and retrieval systems must evolve to address dynamic access needs, adaptability, and security in distributed environments. The '''.seigr''' format fulfills these needs by introducing multi-dimensional, senary-encoded files with embedded metadata and cross-referencing that allow for complex retrieval paths and temporal adaptability. This ensures that data remains robust, easily accessible, and evolves to meet user demand, creating a resilient and self-sustaining digital ecosystem.
+This format is the foundation of the '''Seigr Protocol''', ensuring that data remains '''decentralized, cryptographically verified, and ethically managed''' across the network.
-== Key Features of .seigr Files ==
-The '''.seigr''' format encapsulates several advanced features that ensure scalability, security, and adaptability within the Seigr Urcelial-net:
+== Concept and Structure ==
-* '''Fixed Size of 539 KB''': Each '''.seigr''' file maintains a precise 539 KB size, balancing accessibility across low-power devices and network nodes with the scalability required for large data sets.
+The ''.seigr'' format combines '''biological principles, cryptographic hashing, and modular design''' to form an '''interconnected, evolving''' data ecosystem.
-* '''Senary Encoding with Multi-Layered Data Links''': Utilizing [[Special:MyLanguage/senary|senary encoding (base-6)]], '''.seigr''' files encode data compactly while supporting complex retrieval pathways. Multi-dimensional linking allows segments to interrelate hierarchically and laterally, enabling rapid data access through various paths.
+=== Capsule-Based Execution ===
+Each ''.seigr'' file functions as a '''Seigr Capsule''', operating within the [[Special:MyLanguage/Seigr Capsule Engine (SCE) | Capsule Execution Layer (SCE)]]. This ensures:
-* '''Non-Linear Hash Chaining and Temporal Cross-Referencing''': Files leverage hash-chaining across segments, forming a tamper-resistant, interlinked web. Segments contain metadata that supports adaptive retrieval paths and temporal tracking of file transformations, capturing each version's unique place in the network over time.
+* '''Immutable Capsule Integrity''' → Each ''.seigr'' file maintains '''self-contained execution logic''', ensuring '''data lineage''' and '''cryptographic trust'''.
+* '''Multi-Path Hash Linking''' → Capsules interlink using '''primary and secondary hashes''', ensuring '''resilience''' and '''non-linear data retrieval'''.
-* '''Demand-Based Adaptive Replication''': Each '''.seigr''' file dynamically adjusts its replication frequency based on user demand. This ensures that high-demand segments are readily accessible, while low-demand segments remain minimally replicated, preserving storage resources across the network.
+=== Seigr Cell Inheritance & RE-L Integration ===
+* Every ''.seigr'' file is '''composed of Seigr Cells'''—discrete, interlinked data units.
+* '''RE-L enforcement occurs at the Cell level''', ensuring that '''every contribution retains its licensing, origin, and ethical metadata'''.
+* '''Like DNA sequences in biological organisms, Seigr Cells pass licensing rules through cryptographic linkage''', ensuring '''immutable lineage tracking'''.
-* '''Decentralized Storage with IPFS''': By integrating with [[Special:MyLanguage/IPFS|IPFS]], each '''.seigr''' file is distributed across Seigr Urcelial-net nodes, ensuring data resilience, security, and accessibility without dependence on centralized storage systems.
+=== Generative & Adaptive Data Structure ===
+* '''Evolutionary Storage Model''' → Like biological cells '''storing and transmitting genetic information''', ''.seigr'' files adapt to evolving network conditions.
+* '''RE-L Genetic Print''' → Every ''.seigr'' file '''inherits ethical constraints''' encoded into its '''Seigr Cells''', ensuring '''indelible contributor attribution'''.
-== Multi-Dimensional, Time-Responsive Data Structure ==
-The '''.seigr''' format structures data as a four-dimensional entity, layering metadata, content, and temporal information to allow adaptive, resilient access. This innovative structure supports multi-path data retrieval, contextual connections, and continuous file evolution across time:
+== Seigr Protocol & Cryptographic Structure ==
-* '''Primary and Secondary Links''': Each segment includes primary and secondary hashes that establish non-linear, flexible retrieval paths, enabling assembly from various network access points.
+The '''Seigr Protocol''' governs ''.seigr'' file behavior through a structured, self-verifiable '''data and execution framework'''.
-* '''4D Coordinate-Based Indexing for Multi-Layer Navigation''': Segments may include three-dimensional coordinates for layered, semantic positioning within the data architecture, as well as a fourth dimension for time. This 4D indexing allows '''.seigr''' files to track transformations over time, supporting multi-path access that can adapt to both hierarchical and temporal shifts.
+=== Core Components ===
+* [[Special:MyLanguage/Seigr Metadata|Seigr Metadata]] → Ensures each '''Seigr Cell''' retains distinct, traceable, and interoperable records.
+* [[Special:MyLanguage/Temporal Layering|Temporal Layering]] → Embeds '''time-indexed snapshots''', enabling '''historical reconstruction & rollback'''.
+* [[Special:MyLanguage/Encoder Decoder Module|Encoder/Decoder Module]] → Converts binary data into '''senary (base-6) encoding''' for energy-efficient processing.
-* '''Annotations and Cross-Referencing''': Segments can carry contextual tags and annotations that allow dynamic linking to related resources across the network, creating an interconnected ecosystem for users and applications to explore and build upon.
+=== RE-L Licensing Enforcement ===
+Every ''.seigr'' file contains an '''immutable RE-L enforcement layer''', ensuring:
+* '''Contributor Attribution''' → Every '''Seigr Cell''' retains '''RE-L metadata, permissions, and monetization rules'''.
+* '''Multi-Layer Lineage Tracking''' → Changes are '''cryptographically logged''', preventing data corruption or unauthorized alteration.
-== Temporal Layers: Tracing File Evolution Over Time ==
+=== Mathematical Structure: Multi-Path Hashing ===
+Each ''.seigr'' file maintains '''multi-dimensional hash linking''', ensuring '''fault tolerance and adaptive retrieval'''.
-Each '''.seigr''' file retains a historical record of its transformations, capturing structural or replication adjustments as '''temporal layers'''. These layers act as snapshots of a file's state at different moments in time, enabling Seigr Urcelial-net to support files as dynamic, evolving entities:
+Let:
+* '''H(c)''' be the hash of a Seigr Cell '''c'''.
+* '''H'(c, t)''' represent the cryptographic lineage of '''c''' at time '''t'''.
-* '''Multi-Path Assembly Across Temporal Layers''': Temporal layers catalog the primary and secondary segment hashes for various points in time, supporting flexible file assembly across both spatial and temporal paths.
+Multi-path hash linking ensures:
+<math>
+H'(c, t) = H(c) \oplus H(c_{parent}) \oplus H(t)
+</math>
-* '''Dynamic Routing and Replication Logging''': As segments replicate and adapt to demand, each '''.seigr''' file logs routing and replication metadata within temporal layers. This enables continuous access and integrity even as storage nodes shift over time.
+Where:
+* '''H(c_parent)''' ensures cryptographic inheritance.
+* '''H(t)''' timestamps lineage evolution.
-* '''Adaptive Pathways Based on Temporal Demand''': By monitoring access trends across time, the '''.seigr''' format automatically optimizes frequently accessed segments while preserving baseline copies for archival data.
-== Structure of a .seigr File ==
+== Binary-Senary Hybrid Execution & Sensory Tagging ==
-Each '''.seigr''' file comprises structured metadata and adaptive data layering, supporting retrieval efficiency, integrity, and cross-temporal access:
+The ''.seigr'' format integrates '''Seigr-native processing''' with '''legacy binary execution''', preserving '''data lineage and RE-L governance'''.
-* '''Header''':
+=== Hybrid Execution ===
-  - '''Version''': Specifies the format version, maintaining compatibility as the format evolves.
+* [[Special:MyLanguage/Universal Binary-Senary Bridge (UBSB) | UBSB]] allows seamless execution of '''binary processes''' inside Seigr Capsules.
-  - '''File Type''': Indicates the data type (e.g., binary, text).
+* '''Binary Payload Encapsulation''' ensures '''non-native data can still inherit Seigr’s ethical and security principles'''.
-  - '''Part Index and Total Parts''': Identifies the segment’s position within the full dataset.
-  - '''Primary and Secondary Links''': Hashes for direct and cross-referenced links, creating multi-dimensional data pathways.
-  - '''4D Coordinate Indexing''': Optional three-dimensional placement and a fourth dimension for time indexing, enabling layered navigation within both spatial and temporal frameworks.
-* '''Senary Encoded Data''': Stores the main content as a senary-encoded string, compactly representing the data in base-6.
-* '''Temporal Integrity and Hashing''': Generated using [[Special:MyLanguage/HyphaCrypt|HyphaCrypt]], these integrity checks ensure data consistency across temporal layers and prevent unauthorized tampering.
+=== Sensory-Based Processing ===
+* '''Sensory Metadata Tagging''' → ''.seigr'' files attach '''sensory-executable metadata''', enabling '''AI-driven retrieval and pattern recognition'''.
+* '''Capsule-Based Sensory Abstraction Layer (CBSAL)''' → Facilitates '''context-aware Seigr-native AI interactions'''.
-== Adaptive Replication and Self-Healing Cross-Referencing ==
-The '''.seigr''' format is designed to respond to user demand dynamically and support self-healing pathways for resilient data structure management across the Seigr Urcelial-net:
+== Key Features of .seigr Files ==
-. '''Temporal Multi-Path Cross-Referencing''':
+The ''.seigr'' format incorporates '''advanced resilience, modularity, and cryptographic security'''.
-   - Each segment holds primary and secondary hashes that connect to other segments. These references enable non-linear, multi-path retrieval and allow for multiple reconstruction pathways across spatial and temporal dimensions.
-. '''Demand-Adaptive Replication''':
+{| class="wikitable"
-   - Based on real-time access, segments adjust their replication count to prioritize frequently accessed files while preserving essential data with minimal replication.
+|+ Key Features of .seigr Files
+|-
+! Feature
+! Description
+|-
+| '''Fixed Size (53,194 Bytes)'''
+| Standardized '''data capsule size''' ensures '''predictable replication & efficient retrieval'''.
+|-
+| '''Senary Encoding'''
+| Base-6 encoding '''minimizes energy usage''', aligning with Seigr’s '''eco-conscious computing principles'''.
+|-
+| '''Primary & Secondary Hash Links'''
+| Ensures '''multi-path retrieval, fault tolerance, and non-linear execution tracking'''.
+|-
+| '''Demand-Based Replication'''
+| Capsules replicate '''based on real-time access patterns''', ensuring '''optimal resource allocation'''.
+|-
+| '''IPFS Compatibility'''
+| ''.seigr'' files integrate with '''[[Special:MyLanguage/IPFS | IPFS]]''' for decentralized redundancy.
+|}
-. '''Continuous Availability and Self-Healing''':
+== Adaptive Replication & Self-Healing ==
-   - Integrity checks validate segment availability. Missing or corrupted segments can be reconstructed through alternative paths, ensuring network-wide resilience and continuity.
-== Immune System for Threat Detection and Response ==
+=== Biologically-Inspired Replication ===
+'''Like neural networks adjusting synaptic strength, ''.seigr'' capsules replicate adaptively''' based on '''demand & access frequency'''.
-To ensure proactive, cellular-like defense against integrity threats, the '''.seigr''' format includes an advanced, decentralized [[Special:MyLanguage/Immune System|Immune System]]. This system functions much like an organism's immune response, deploying distributed "cells" (nodes) to continuously monitor, detect, and respond to potential file integrity threats.
+Let:
+* '''A''' be the capsule '''access rate'''.
+* '''R''' be its '''redundancy factor'''.
+* '''S''' be its '''security classification'''.
-The [[Special:MyLanguage/Immune System|Immune System]] works in tandem with the temporal and adaptive replication features to create a resilient environment for '''.seigr''' files, detecting anomalies, triggering security replications, and initiating rollbacks when necessary. This self-healing and responsive approach ensures that integrity breaches are addressed dynamically, enhancing network-wide stability and resilience.
+The probability of replication follows:
+<math>
+P_{replicate} = \frac{A}{R + S}
+</math>
-== Hyphen Network and Decentralized Data Management ==
+=== Self-Healing & Integrity Enforcement ===
+If corruption is detected:
+* '''Multi-Path Hash Recovery''' → Capsules rebuild from '''alternative hash references'''.
+* '''Dynamic Regeneration''' → Seigr Cells '''self-reconstruct''' by cross-verifying with '''parent nodes'''.
-Participants in the Seigr Urcelial-net, known as [[Special:MyLanguage/Hyphens|Hyphens]], play a critical role in maintaining, scaling, and verifying '''.seigr''' files:
+== Node Identity & Trust-Based Execution ==
-* '''Data Caching and Scaling Access''': Hyphens locally cache segments to ensure high availability, dynamically replicating high-demand segments while tracking access trends.
+Each ''.seigr'' file is bound to '''Seigr's cryptographic identity model''', ensuring '''trusted execution'''.
-* '''Temporal Replication and Demand Scaling''': Hyphens use temporal access data to scale replication as needed, creating more copies for high-demand segments while maintaining minimal copies for archived data.
+{| class="wikitable"
+|+ Node Identity & Trust-Based Execution
+|-
+! Security Feature
+! Description
+|-
+| '''Hardware-Bound Cryptographic Signatures'''
+| Prevents unauthorized execution '''outside verified Seigr nodes'''.
+|-
+| '''Network-Wide Trust Enforcement'''
+| Execution lineage tracking '''prevents unauthorized capsule replication'''.
+|-
+| '''Seigr Hardware Identity Layer (SHIL)'''
+| '''Automatically authenticates and validates''' all ''.seigr'' executions.
+|}
-* '''Integrity Verification Across Temporal Layers''': Hyphens validate segment integrity with temporal checks, maintaining continuity and replacing corrupted files, supporting the network's self-healing capacity.
-== Encoder/Decoder Module with Senary Encoding and Dynamic Retrieval ==
+== RE-L Genetic Print & Contribution Unit (CU) Tracking ==
-The [[Special:MyLanguage/Encoder/Decoder Module|Encoder/Decoder Module]], using [[Special:MyLanguage/HyphaCrypt|HyphaCrypt]], supports multi-layered senary encoding and flexible decoding for adaptive retrieval across Seigr Urcelial-net:
+=== Inherited RE-L Licensing at Every Level ===
+Each '''Seigr Cell''' inside a ''.seigr'' file retains:
+* '''Immutable Contribution Units (CUs)''' that track '''creator attributions, role definitions, and licensing metadata'''.
+* '''Adaptive Contribution Units (ACUs)''' for '''layered modifications without altering core lineage'''.
+* '''RE-L Automated Enforcement''' → Unauthorized licensing changes trigger '''Hyphen Network validation'''.
-* '''Temporal Senary Encoding''': Encodes binary data in senary format, embedding primary and secondary hashes with temporal layers for optimized data retrieval.
+'''Mathematically:'''
+<math>
+L_{inherit} = L_{parent} \oplus H(CU) \oplus H(ACU)
+</math>
+where:
+* '''L_{inherit}''' is inherited licensing.
+* '''H(CU)''' enforces Contribution Unit rules.
+* '''H(ACU)''' tracks modifications.
-* '''Flexible Multi-Path Decoding''': Decoding pathways leverage segment interconnections across space and time, reconstructing data dynamically and making the data retrieval process resilient to network changes.
-== Security and Integrity in the .seigr Format ==
+== Conclusion ==
-The '''.seigr''' format uses sophisticated security protocols to ensure data integrity and adaptability in a decentralized, temporally aware environment:
+The ''.seigr'' format '''redefines digital integrity''' through '''modular evolution, ethical governance, and cryptographic enforcement'''. '''Every ''.seigr'' file is a living, interwoven data entity''', inheriting RE-L '''like genetic markers''' to ensure '''a sustainable, decentralized, and ethically governed future'''.
-* '''Temporal Hash Chaining and Adaptive Salting''': Hash chains with adaptive salting provide tamper resistance, ensuring unauthorized changes are detectable across the network's interconnected segments and temporal layers.
-* '''Encryption Compatibility''': Files can be encrypted with [[Special:MyLanguage/HyphaCrypt|HyphaCrypt]], securing sensitive data with temporal access control and retaining decentralized sharing capabilities.
-== Future Potential ==
-The '''.seigr''' format serves as a foundation for evolving decentralized applications and data structures. As the Seigr Urcelial-net grows, it may incorporate advanced cryptographic layers, more complex metadata relationships, and evolving temporal data dynamics, enhancing both adaptability and resilience.
-== Conclusion ==
-The '''.seigr''' format embodies Seigr’s vision of a dynamic, resilient, and interconnected digital ecosystem. By adopting a multi-dimensional, time-responsive architecture, it transcends traditional data storage and retrieval, creating a network inspired by the mycelium's natural resilience and adaptability.
-Inviting scientists, researchers, developers, and contributors to participate, the '''.seigr''' format offers a framework for sustainable and community-driven digital infrastructure. As data evolves alongside its network, the '''.seigr''' format ensures a future-ready, adaptable data landscape for the next era of decentralized technology.
+== Explore Further ==
+* [[Special:MyLanguage/Seigr Protocol | Seigr Protocol]]
+* [[Special:MyLanguage/Rebel Earthling License (RE-L) | RE-L Licensing]]
+* [[Special:MyLanguage/Seigr Capsules | Seigr Capsules]]
+* [[Special:MyLanguage/Weighted Consistency & Alignment Score (WCAS) | Voting in Seigr]]