railiance-fabric/registry/capabilities/capability.railiance.fabric-graph.md

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance, promotion_history

id	name	summary	owner	status	domain	tags	maturity	external_evidence	discovery	availability	relations	evidence	consumer_guidance	promotion_history
capability.railiance.fabric-graph	Railiance Fabric Ecosystem Graph	Models the durable infrastructure-responsibility graph of the Railiance netkingdom: schemas, discovery tools, registry services, graph queries, and State Hub export contracts for services, machines, repos, deployables, endpoints, ownership, dependencies, and bindings.	railiance-fabric	draft	financials	railiance graph ownership discovery	discovery availability current target confidence rationale D3 D5 medium README and SCOPE.md document the ecosystem graph model bounded by financial/operational accountability (who pays, who is accountable), with king/lord/tenant ownership concepts referenced in docs/FabricDiscoveryAndUpdate.md. current target confidence rationale A1 A3 medium Python package (`railiance-fabric`) providing a declaration loader and validator; consumed as a library, no hosted service documented yet.	completeness reliability level confidence basis satisfied_expectations broken_expectations out_of_scope_expectations C1 low scope_vs_intent_and_consumer_expectations ecosystem graph declaration loader and validator schemas for services/machines/repos/deployables/endpoints/ownership/dependencies/bindings level confidence basis known_reliability_risks R0 low consumer_quality_signals discovery/rebuild/update-loop architecture documented as still evolving per docs/FabricDiscoveryAndUpdate.md	intent includes excludes assumptions use_cases research_memos Let repos declare services, capabilities, interfaces, dependencies, and bindings in source-controlled files, and model the resulting durable infrastructure-responsibility graph across the Railiance ecosystem. ecosystem graph schema and declaration loader/validator State Hub export contracts for the graph actual infrastructure provisioning (see railiance-infra, railiance-cluster)	current_level target_level current_artifacts target_artifacts consumption_modes A1 A3 Python package (`railiance-fabric`) library import cli (validation)	depends_on supports related_to	documentation tests consumer_feedback bug_reports incidents README.md SCOPE.md docs/FabricDiscoveryAndUpdate.md tests/	recommended_for not_recommended_for known_limitations Railiance repos wanting to declare their place in the ecosystem ownership/dependency graph needs for actual infrastructure provisioning (see railiance-infra/-cluster) discovery/rebuild/update-loop architecture still evolving

Railiance Fabric Ecosystem Graph

Overview

railiance-fabric models the durable infrastructure-responsibility graph of the Railiance netkingdom — who pays for infrastructure, who is accountable for it, and which durable interfaces create value across boundaries — via schemas, a declaration loader/validator, and State Hub export contracts.

Assessment notes

Discovery

README and SCOPE.md document the ecosystem graph model bounded by financial/operational accountability (who pays, who is accountable), with king/lord/tenant ownership concepts referenced in docs/FabricDiscoveryAndUpdate.md.

Availability

Python package (railiance-fabric) providing a declaration loader and validator; consumed as a library, no hosted service documented yet.

Completeness

First-pass honest assessment from the REUSE-WP-0017 coverage campaign (reuse-surface). No external consumer feedback exists yet; levels reflect scope-vs-intent documentation quality, not internal code quality.

Reliability

No production consumer telemetry exists yet; reliability level is intentionally conservative pending REUSE-WP-0019 reuse-telemetry evidence.

Promotion checklist

• ID follows capability.<domain>.<name> pattern
• Maturity enums match specs/CapabilityMaturityStandard.md
• external_evidence is populated separately from maturity
• Relations reference valid capability IDs (none yet)
• Index entry added in registry/indexes/capabilities.yaml