coulomb/railiance-fabric
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: finish financial fabric reset guidance

Browse Source
This commit is contained in:
Bernd Worsch
2026-05-24 01:37:05 +02:00
parent 9717b18b02
commit f4aa4aa996
16 changed files with 304 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/registry-onboarding.md
View File

@@ -1,9 +1,15 @@
# Registry Onboarding
Multi-repo onboarding uses a repo-owned manifest to register ecosystem
Multi-repo onboarding uses an operator-owned manifest to register ecosystem
repositories with a running Railiance Fabric registry and to push graph and
library inventory when the local checkout has the required inputs.
Repo-local declarations remain useful self-description evidence. They should
not be treated as the default authority for external fabric membership,
ownership, tenant boundaries, or cross-boundary utility relations. Those belong
to the accountability-root discovery model described in
`docs/FabricDiscoveryAndUpdate.md`.
## Run The Railiance Manifest
Start the registry:
@@ -57,7 +63,7 @@ registration.
Each repository entry is registered first. If the checkout is unavailable or has
no Fabric declarations yet, the command leaves the repo registered and reports a
warning. This lets the registry represent known repos before every repo has
adopted local declarations.
published local evidence.
When declarations exist, the command validates them, builds a graph snapshot,
and posts it to:
@@ -67,9 +73,9 @@ POST /repositories/{repo_slug}/snapshots
```
The first Railiance manifest keeps the seed ecosystem graph in
`railiance-fabric` and registers adjacent repos as known sources. As those repos
adopt repo-local `fabric/` declarations, they can be synced without changing the
registry API.
`railiance-fabric` and registers adjacent repos as known sources. As discovery
roots mature, adjacent repos can contribute local evidence without making each
repo responsible for the whole external fabric relation model.
`registry/local-repos.yaml` is a broader local-host manifest. It is generated
from active State Hub repo records whose local path exists on the current WSL