generated from coulomb/repo-seed
Add railiance-fabric conformance support pack
This commit is contained in:
71
infospace/evaluations/railiance-fabric/conformance-pack.yaml
Normal file
71
infospace/evaluations/railiance-fabric/conformance-pack.yaml
Normal file
@@ -0,0 +1,71 @@
|
||||
id: conformance/railiance-fabric
|
||||
title: Railiance Fabric Canon Conformance Pack
|
||||
status: candidate
|
||||
consumer: railiance-fabric
|
||||
purpose: Prepare canon-side support for refactoring railiance-fabric entity and edge capture for conformance, reasoning, and visualization.
|
||||
created_by_workplan: ITC-WP-0008
|
||||
conformance_mode: pre-refactor
|
||||
canon_anchors:
|
||||
- model/landscape
|
||||
- model/network
|
||||
- model/data
|
||||
- model/devsecops
|
||||
- model/observability
|
||||
- model/governance
|
||||
- model/security
|
||||
- model/task
|
||||
- model/purpose-demand-extension
|
||||
- standard/tagging
|
||||
- profile/small-saas
|
||||
pack_components:
|
||||
capture_criteria: evaluations/railiance-fabric/entity-edge-capture-criteria.yaml
|
||||
mapping_expectations: evaluations/railiance-fabric/mapping-expectations.yaml
|
||||
visualization_examples: evaluations/railiance-fabric/visualization-examples.yaml
|
||||
consumer_workplan_brief: evaluations/railiance-fabric/consumer-workplan-brief.md
|
||||
capture_surfaces:
|
||||
- landscape entities and their ownership boundaries
|
||||
- runtime resources, deployments, repositories, pipelines, and artifacts
|
||||
- network zones, endpoints, reachability, paths, and flows
|
||||
- datasets, datastores, lineage, residency, and processing purpose
|
||||
- observability signals, alerts, incidents, dashboards, and evidence
|
||||
- governance policies, controls, reviews, exceptions, and decisions
|
||||
- security findings, exposure, attack paths, and mitigations
|
||||
- tasks created from gaps, findings, remediation, or evolution pressure
|
||||
- consumer purposes, demand signals, purpose fit, and scope pressure
|
||||
readiness_gates:
|
||||
- id: gate/entity-identity
|
||||
title: Captured nodes have stable canonical identity.
|
||||
required: true
|
||||
expects:
|
||||
- Every canonical node has id, kind, title, source, owner or steward, provenance, and canon anchor.
|
||||
- id: gate/edge-semantics
|
||||
title: Captured edges distinguish canonical relationships from display-only edges.
|
||||
required: true
|
||||
expects:
|
||||
- Every canonical edge has type, source, target, source artifact, confidence, and evidence status.
|
||||
- id: gate/visualization-boundary
|
||||
title: Visualization metadata does not become canon meaning.
|
||||
required: true
|
||||
expects:
|
||||
- Layout, color, cluster, rank, and collapse edges are marked display_only.
|
||||
- id: gate/evidence-trace
|
||||
title: Claims can be traced to evidence, signal, or explicit gap.
|
||||
required: true
|
||||
expects:
|
||||
- Captured entities and edges carry evidence references or known gap status.
|
||||
- id: gate/purpose-pressure
|
||||
title: Fabric demand can feed canon evolution without silently changing scope.
|
||||
required: true
|
||||
expects:
|
||||
- Railiance-fabric declares purposes, use cases, demand signals, purpose fit, and requested evolution.
|
||||
output_expectations:
|
||||
- completed Canon Interface Card for railiance-fabric
|
||||
- entity category mapping export
|
||||
- edge category mapping export
|
||||
- clean graph examples and corrected bad graph examples
|
||||
- evidence bundle or explicit evidence gaps
|
||||
- consumer-side workplan created in the railiance-fabric repo
|
||||
non_goals:
|
||||
- Refactor railiance-fabric in this repo.
|
||||
- Choose railiance-fabric storage, graph database, UI, or rendering technology here.
|
||||
- Treat visual grouping as canonical meaning.
|
||||
Reference in New Issue
Block a user