Dynamic Governance Agentic Formation (DGAF) — a research and implementation repository for agent orchestration, evaluation, provenance, and governance controls.
Epistemic status: This README describes repository scope and the current pre-freeze governance state. Individual claims of validation, certification, performance, standards alignment, or commercial suitability require exact evidence and defined scope. Historical certifications remain scoped to the SHA/run/deployment that produced them and are not current certification without fresh evidence.
The DGAF/PDMAL experimental track remains PRE-FREEZE. The corrected pilot apparatus and supporting governance controls are present on main, but the current candidate has not been freeze-verified. No new experimental freeze exists, pilot authorization has not been granted, and empirical N = 0.
The historical implementation freeze 3510b86889cd341f7a7cf9ab684fd37b2fafd758 remains preserved as historical evidence only. It must not be described as the current freeze of the corrected apparatus.
The current executable verification candidate is e6beeb66335e1b50a239697badab22dab50eb5ba. It incorporates the current P8 integrity corrections and regression coverage. The candidate is deployed to Vercel as production deployment dpl_HgSv9hTrvMNBHxboDhkkvHKeogc5 and is READY, but formal authenticated P2/P6a runtime verification, P7 formal adoption/binding, durable custody, P9 independent verification, and new freeze verification remain incomplete. Documentation-only successors do not redefine the executable apparatus; any further substantive apparatus change requires a new candidate identity and re-verification.
The repository is also undergoing an ecosystem architecture pass separating DGAF implementation from the broader Pattern Commons and from commercialization, trademark, privacy, and security boundaries. These documentation changes do not themselves advance experimental gates.
For the authoritative gate board and remaining sequence, see docs/PROJECT_STATUS.md and docs/CURRENT_STATE.md. For pattern architecture, see docs/PATTERN_COMMONS_ARCHITECTURE.md. For openness/commercialization boundaries, see docs/GOVERNANCE/DGAF_COMMERCIALIZATION_OPENNESS_BOUNDARY.md. For the asset-level ecosystem inventory, see docs/GOVERNANCE/DGAF_ASSET_LEVEL_BOUNDARY_INVENTORY_2026-08-25.md. For future trademark/certification governance, see docs/GOVERNANCE/DGAF_TRADEMARK_AND_CERTIFICATION_POLICY.md.
DGAF contains governance and evaluation components, agent specifications, control/gate definitions, provenance practices, epistemic auditing, vocabulary management, and experimental research artifacts. DGAF is the implementation/governance substrate; it is not the universal owner of every pattern, taxonomy, template, or research artifact in the surrounding ecosystem.
- DGAF — Dynamic Governance Agentic Formation.
- AHG — Adaptive Harmonic Governance. Historical/conflicting expansions remain historical unless explicitly promoted by current governance.
- PDMAL / PDMA-L — Phi-Driven Multi-Agent Lattice. The term refers to the lattice/control research track; current evidence does not establish a complete Byzantine Fault Tolerance protocol merely from the topology.
- NDR — a project pattern namespace/family within the broader Pattern Commons architecture, not the entire ecosystem pattern corpus.
- Pattern Commons — proposed ecosystem-level layer for pattern identity, provenance, aliases/equivalence, epistemic status, and evidence relationships across repositories.
- AXIS — Agent X-axis Invariant Spectrum.
- FLAG-02 — historical identifier associated with the former 340% coordination-gain claim. Current evaluation-mode terminology is qualitative. New documents must not introduce FLAG-02 as a current identifier for either meaning.
Historical documents may retain their original terminology when necessary for provenance, but they must be treated as historical rather than silently reinterpreted as current state.
DGAF permits agents and components to consume and reason over an approved ontology. They must not silently introduce, redefine, or assert ontology outside the authorized semantic layer.
The governing progression is:
defined → observed → supported → verified → authorized → canonical
Operational documentation must distinguish representation, classification, policy status, epistemic status, and ontological assertion. New terminology or semantic categories are candidate vocabulary until provenance and authorization establish canonical status. Agent repetition, confidence, or wording does not create semantic authority.
Ontology drift is treated as a distinct semantic-drift class: an unauthorized change in effective vocabulary, entity boundaries, relations, or semantic commitments. The broader semantic-risk taxonomy is definition drift, ontology drift, epistemic drift, policy drift, and provenance drift.
Semantic/ontological detection is not automatically a blocking gate. A detector must be empirically characterized before it becomes threshold-bearing or gate-bearing. This control does not alter the experimental state: PRE-FREEZE / FAIL-CLOSED / N=0 / NO FREEZE / PILOT AUTHORIZATION NOT GRANTED.
Claims are classified according to the repository standard:
DEFINED → IMPLEMENTED → COMPUTED → VERIFIED → ATTESTED → HISTORICAL → HYPOTHESIS → METAPHOR → UNSUPPORTED → DEPRECATED
A mathematical term, external framework name, benchmark number, deployment, registry entry, commercial status, or agent role does not by itself establish implementation, validation, legal compliance, safety, certification, or independent verification.
- Agent orchestration and control-plane design
- Evaluation and quality-assurance tooling
- Provenance and traceability
- Governance gates and deployment controls
- Epistemic auditing and vocabulary management
- Semantic/ontological boundary governance
- Pattern Commons integration and cross-repository reconciliation
- Experimental mathematical and structural research
- Open-source commercialization and evidence-preserving governance
DGAF aims to keep the public reference implementation sufficiently complete for independent cloning, inspection, execution, and evaluation. Legitimate commercial differentiation may reside in managed operations, integration, assurance, support, hosting, specialized tooling, customer-specific configurations, training, and future certification programs. Public scientific/technical claims must retain enough evidence for independent evaluation even when adjacent operational assets are commercial or private.
The repository is licensed under Apache-2.0. See LICENSE for the legal terms. The license does not grant trademark rights; future official, certification, or endorsement claims bearing the DGAF name require separate governance and should not be inferred from repository status or project attestation.
- Current State
- Project Status
- PDMAL Current Control State
- Authoritative PDMAL Task Specification
- PDMAL Evidence Index
- Evidence Ladder Policy
- PDMAL Experiment Protocol
- Freeze Manifest Template
- Propagation Consistency Control
- Documentation Reconciliation
- Test Execution Readiness
- P3–P6 Freeze Readiness
- P7 Primary Contrast Adjudication
- Candidate Runtime Verification
- NDR Research Program Charter — Current Status Addendum
- Freeze Packet Template
- Pattern Commons Architecture
- Commercialization & Openness Boundary
- Asset-Level Boundary Inventory
- Trademark & Certification Policy
- CROSS_REF
The repository contains deterministic/unit tests, pilot execution-contract tests, artifact/schema controls, governance consistency checks, propagation checks, and CI workflows. Existence of a test is not evidence that the test has passed. Current candidate verification must identify the exact candidate SHA, execution environment, deployment where applicable, run identifier, and retained evidence artifact.
- P1 Candidate integrity — PARTIAL
- P2 Execution contract — PARTIAL
- P3 Artifact contract — PARTIAL
- P4 Security/blinding integrity — PARTIAL
- P5 Provenance/reproducibility — PARTIAL
- P6 Durable evidence custody — OPEN
- P7 Scientific target specification — PARTIAL / FORMALLY OPEN; primary contrast technically selected, authority adoption pending
- P8 Analysis lock — OPEN / FAIL-CLOSED
- P9 Independent verification — NOT EXECUTED
- New freeze — NOT CREATED
- Pilot authorization — NOT GRANTED
- Empirical N — 0
Do not infer repository-wide validation from a component-level test, historical attestation, deployment existence, README text, funding badge, commercial status, or certification language.
Historical runtime, P2, P6a, and characterization records remain valid only for the exact source/deployment/run they document. In particular, retained historical results are not current-candidate verification.
Related repositories are separate tracks. Shared terminology does not imply implementation equivalence or cross-repository validation. See CROSS_REF.md for the current cross-reference and epistemic boundary index.
GitHub Sponsors configuration is present through .github/FUNDING.yml. Sponsorship supports maintenance and development; it does not confer ownership, certification, endorsement, or special evidence status.
See LICENSE for the repository's applicable license.
Developed by Ndr / Ender Hensel (ndrorchestration).