coulomb/railiance-fabric
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

CUST-WP-0055 T06/T07: workplan-first fabric source docs and archive notes
All checks were successful
CI Smoke / host-smoke (push) Successful in 2s
Details
CI Smoke / container-smoke (push) Successful in 7s
Details

Browse source 
Update catalog, integration docs, and fabric capability declarations to
use workplan terminology. Add archive grandfather notes.
This commit is contained in:
tegwick 2026-07-08 20:26:24 +02:00
parent 3fff3e4209
commit 0507b0861b
35 changed files with 65 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/FabricDiscoveryAndUpdate.md
View file

@ -88,7 +88,7 @@ responsibility move to another lord.
A view is a diagnostic or informational slice through the graph.
Views can filter by repository, service, environment, machine, endpoint, tenant,
workstream, deployment stack, or business capability. Views do not define fabric
workplan, deployment stack, or business capability. Views do not define fabric
membership and should not mutate fabric boundaries.
Zone views are a special kind of view. They group the subgraph by deployment

2
docs/ecosystem-registry-service.md
View file

@ -57,7 +57,7 @@ The registry service should not own:
- deployment orchestration
- service provisioning
- policy enforcement gates before the model has adoption
- replacing State Hub workstreams, tasks, progress, or planning state
- replacing State Hub workplans, tasks, progress, or planning state
- replacing a developer portal
## Initial Data Model

2
docs/financial-fabric-operator-guide.md
View file

@ -166,7 +166,7 @@ secret roots rather than asking each repo to own all external relations.
## State Hub Handoff
State Hub is a read model for Fabric topology. It should ingest Fabric exports,
link them to repos/workstreams/tasks, and expose dashboard/search views. It
link them to repos/workplans/tasks, and expose dashboard/search views. It
should not author ownership, fabric membership, or utility boundaries.
Until `STATE-WP-0051` is implemented:

6
docs/state-hub-integration.md
View file

@ -13,7 +13,7 @@ ownership, fabric membership, or cross-boundary utility relations.
| Deployment/accountability roots | Durable evidence of infrastructure, deployment, ownership, utility, and payment responsibility | State Hub task state |
| Participating repos | Self-description evidence such as code, manifests, API contracts, package metadata, and legacy `fabric/` declarations | All external deployment/fabric relations |
| Railiance Fabric | Schemas, discovery, validation, graph construction, accepted snapshots, exports | State Hub tasks/progress/decisions |
| State Hub | Read-model storage, links to repos/workstreams/tasks/progress, dashboard/search views | Editing Fabric topology or inventing ownership |
| State Hub | Read-model storage, links to repos/workplans/tasks/progress, dashboard/search views | Editing Fabric topology or inventing ownership |
The flow is:
@ -235,8 +235,8 @@ State Hub should enrich graph nodes by matching:
- `node.repo` -> `managed_repos.slug`
- `node.domain` -> `domains.slug`
- workplan source links -> `workstreams.slug` or file-backed workplan index
- progress events -> `repo_id` and related workstream/task when available
- workplan source links -> `workplans.slug` or file-backed workplan index (legacy alias: `workstreams.slug`)
- progress events -> `repo_id` and related workplan/task when available
These links are annotations on the read model. They should never overwrite the
Fabric export or source evidence.