railiance-fabric/docs/accountability-root-manifest.md

Accountability Root Manifest

The accountability root manifest is the handoff between the financial Fabric model and the discovery/update loop.

It answers where discovery starts. A manifest names the netkingdom, actors, fabric boundaries, and durable roots that can prove repositories, deployment realities, service configuration, endpoint contracts, backup/recovery evidence, and secret-root metadata. It does not collect live telemetry and it does not make State Hub the authoring surface for topology.

Schema:

schemas/accountability-root-manifest.schema.yaml

Current Railiance manifest:

fabric/discovery/railiance-accountability-roots.yaml

Tenant/subfabric example:

examples/discovery/accountability-root-manifest.yaml

Required Sections

• netkingdom: root id, name, and king actor.
• actors: king, lord, tenant, operator, or steward actors.
• fabrics: fabric and subfabric boundaries.
• discovery_roots: durable roots such as State Hub repo inventory, Gitea organizations, registry manifests, host paths, repo checkouts, deployment automation, endpoint contracts, backup/recovery evidence, and secret-root metadata.
• refresh: cadence and trigger hints for the future update loop.

Boundary Rules

The current Railiance manifest has one active fabric: fabric.railiance.primary. Future tenant subfabrics are added under that fabric by adding a tenant actor, a Subfabric, and subfabric-scoped discovery roots. This does not change the root fabric criterion: the fabric boundary still rests on financial and operational accountability.

Discovery roots should state safe_discovery explicitly. Secret and backup roots should use metadata_only or explicit_review; adapters must never read secret values or operational telemetry while building Fabric graph evidence.