FractalOps Constitution

FractalOps Constitution

FractalOps is the organization meta-control plane.

This document is L0: constitutional law.
Everything below it is either L1 contract or L2 execution.

1. Product Law

FractalOps exists to keep one stable operating grammar:

onboarding -> work -> proposal -> proof -> reflective improvement

Concrete projects and stacks are forcing functions. They do not redefine the product.

2. Ownership Law

FractalOps owns:

• Portal workflow and command-center UX
• Proposal Plane lifecycle and approval boundary
• ontology-aligned read models and graph projection contracts
• access topology and recovery surfaces
• Chronicle evidence indexing and proof lookup
• Ouroboros scheduling and Agent HUD

FractalOps does not allow secondary tools to become competing truth owners.

3. Non-Ownership Law

The following tools remain consumers, execution planes, or adapters:

• Daytona
• Penpot
• Nexus
• PlaywrightGrid
• DataHub
• ClickHouse warehouse
• PostHog
• OpenTelemetry

Non-ownership means these tools may expose or execute truth, but may not redefine the authoritative contract they consume.

4. Mutation Law

• Every non-read AI path must bind to a proposal.
• Proposal Plane is the only legal mutation gate.
• API routes may queue, validate, or reject. They may not perform proposal-bound side effects directly.
• Temporal owns execution for proposal-bound work.
• Temporal owns execution for proposal-bound work.

5. Proof Closure Law

Proof is closed only when all three planes remain queryable:

1. FractalOps Semantics graph/lineage identity
2. ClickHouse warehouse fact or warehouse proof
3. Chronicle evidence long-term provenance

No single plane may claim proof completion alone.

6. Truth-Plane Law

• Git is the normative desired-state source.
• OpenBao is the secret source of truth.
• Semantics is the graph and lineage truth plane.
• DataHub is the catalog and lineage accumulation plane fed by project RDF steward agents and may not own identity, SCIM/JIT, mutation, or proof authority.
• ClickHouse warehouse stores the same project RDF steward lifecycle as queryable events/facts and remains the warehouse fact and warehouse proof plane.
• PostHog and OpenTelemetry are distributed event sources. They must emit or be mapped to global ontology ids before their project-local events accumulate in ClickHouse.
• Chronicle evidence is the long-term proof plane.
• Portal is the primary human workflow surface.
• Ouroboros is the reflective loop that improves the same product through compact Agent HUD.

7. Bounded-Context Law

The canonical bounded contexts are:

• Constitution
• Proposal Plane
• Identity
• Access
• Semantics
• Evidence
• Portal Experience
• Orchestration
• Policy
• Infra Topology

Domain meaning must stay inside the correct context. Interface polish must not redefine domain contracts.

8. Naming Law

The canonical public vocabulary is:

• Portal
• Proposal Plane
• Semantics
• DataHub
• ClickHouse warehouse
• Chronicle evidence
• Ouroboros
• Agent HUD
• access_recovery
• lineage_join_gap
• project spine
• daytona entry

Generic DW wording is illegal in user-facing and agent-facing product grammar.

9. Exception Law

Operational exceptions are allowed only as time-bounded debt.

Every exception must declare:

• id
• reason
• risk
• owner
• introduced_by
• expires_at
• removal_condition

Expired exceptions are constitutional failures.

10. Merge Court Law

No change is merge-complete without:

• proposal_key
• evidence_key
• affected_truth_planes
• approval_class
• rollback_class
• constitutional_pass

PRs are verdict carriers, not narrative status reports.

11. Layer Law

• L0 Constitution: product law and invariants
• L1 Contracts: schemas, compatibility, and examples
• L2 Execution: runtime code, adapters, workflows, UI, infra

L2 must fail if it violates L1.
L1 must fail if it violates L0.