Building Rules That
Outlast One Product
Aregis is contributing practical delivery experience to an open standards effort for accountable work, evidence, and contribution. The standard is still in active development and has not yet been published or certified.
Who Does What
The organizations contributing technology or delivery experience should not have sole authority to declare their own work a standard.
PraSaga Foundation
Working-group hostHosts the DAO SagaStandards Working Group, where contributed specifications can be reviewed, changed, accepted, or declined through the group's process.
SagaHalla
Technology contributorContributes specifications and reference implementations related to GAME Plan, Aregis's planning and delivery system; Saga Agent, an AI agent for clearly bounded tasks under human review; and the broader operating architecture.
Aregis
Delivery contributorContributes lessons and requirements from program management, regulated work, and real-project testing, and intends to adopt applicable published standards.
Why Work Toward an Open Standard
Important project records should remain understandable and portable even when tools, vendors, or teams change. A shared specification can define the meaning of work, evidence, decisions, and contribution independently from any one product, but that benefit depends on review, testing, governance, and adoption that are still ahead.
Principles Guiding the Work
These principles describe the direction of the standards effort. They are not a claim that every planned capability has already been implemented.
Claims Need Evidence
A capability should be described as supported only when there is appropriate implementation and test evidence behind it. Otherwise, its limits should remain visible.
Gaps Stay Visible
A missing capability or unresolved risk should be recorded and addressed, not hidden by changing the definition after the fact.
Real Cases Inform the Design
Specifications should be exercised against practical end-to-end cases before they are treated as mature or ready for broad adoption.
Contributors Do Not Approve Themselves
A proposal remains a contribution until the relevant governance process reviews and accepts it. Contribution is not the same as ratification.
Work Still to Be Resolved
The broader architecture raises questions that require technical, legal, operational, and governance work, including:
- How contribution can be recognized fairly across people, sponsors, service firms, and capital providers.
- How durable evidence records can coexist with privacy, confidentiality, retention, and deletion obligations.
- Which capabilities require shared infrastructure and which should remain inside client-controlled environments.
- How identity, authority, review, and dispute resolution should work across organizations and jurisdictions.
These questions do not prevent Aregis from delivering current program-management or regulated-industry services. They define work that must be completed before broader infrastructure claims are made.
Contribute Through Real Work
Practical engagements and real-project testing help reveal which rules are useful, which assumptions fail, and what controls organizations actually need.
Join the Aregis Network →Organizations evaluating Aregis can request additional information at admin@aregis.io.