---
id: capability.railiance.fabric-graph
name: Railiance Fabric Ecosystem Graph
summary: '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.'
owner: railiance-fabric
status: draft
domain: financials
tags:
- railiance
- graph
- ownership
- discovery
maturity:
  discovery:
    current: D3
    target: D5
    confidence: medium
    rationale: 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:
    current: A1
    target: A3
    confidence: medium
    rationale: Python package (`railiance-fabric`) providing a declaration loader and validator; consumed
      as a library, no hosted service documented yet.
external_evidence:
  completeness:
    level: C1
    confidence: low
    basis: scope_vs_intent_and_consumer_expectations
    satisfied_expectations:
    - ecosystem graph declaration loader and validator
    - schemas for services/machines/repos/deployables/endpoints/ownership/dependencies/bindings
    broken_expectations: []
    out_of_scope_expectations: []
  reliability:
    level: R0
    confidence: low
    basis: consumer_quality_signals
    known_reliability_risks:
    - discovery/rebuild/update-loop architecture documented as still evolving per docs/FabricDiscoveryAndUpdate.md
discovery:
  intent: 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.
  includes:
  - ecosystem graph schema and declaration loader/validator
  - State Hub export contracts for the graph
  excludes:
  - actual infrastructure provisioning (see railiance-infra, railiance-cluster)
  assumptions: []
  use_cases: []
  research_memos: []
availability:
  current_level: A1
  target_level: A3
  current_artifacts:
  - Python package (`railiance-fabric`)
  target_artifacts: []
  consumption_modes:
  - library import
  - cli (validation)
relations:
  depends_on: []
  supports: []
  related_to: []
evidence:
  documentation:
  - README.md
  - SCOPE.md
  - docs/FabricDiscoveryAndUpdate.md
  tests:
  - tests/
  consumer_feedback: []
  bug_reports: []
  incidents: []
consumer_guidance:
  recommended_for:
  - Railiance repos wanting to declare their place in the ecosystem ownership/dependency graph
  not_recommended_for:
  - needs for actual infrastructure provisioning (see railiance-infra/-cluster)
  known_limitations:
  - discovery/rebuild/update-loop architecture still evolving
promotion_history: []
---

# 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

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