Add railiance-fabric conformance support pack

infospace/evaluations/railiance-fabric/consumer-workplan-brief.md

@@ -0,0 +1,56 @@
+---
+id: conformance/railiance-fabric/consumer-workplan-brief
+title: Railiance Fabric Consumer Workplan Brief
+status: candidate
+consumer: railiance-fabric
+conformance_pack: conformance/railiance-fabric
+---
+
+# Railiance Fabric Consumer Workplan Brief
+
+## Purpose
+
+Use this brief as the seed for a railiance-fabric repo workplan. The refactor
+and implementation workplan belongs in the railiance-fabric repository, not in
+InfoTechCanon.
+
+## Goal
+
+Refactor railiance-fabric entity and edge capture so graph visualization stays
+useful while canonical meaning remains clean, traceable, and reusable.
+
+## Canon Inputs
+
+- `infospace/evaluations/railiance-fabric/conformance-pack.yaml`
+- `infospace/evaluations/railiance-fabric/entity-edge-capture-criteria.yaml`
+- `infospace/evaluations/railiance-fabric/mapping-expectations.yaml`
+- `infospace/evaluations/railiance-fabric/visualization-examples.yaml`
+- `infospace/agent/templates/canon-interface-card.template.yaml`
+- `infospace/examples/consumer-purpose-portfolio.yaml`
+
+## Workplan Tasks For Railiance Fabric
+
+1. Complete a Canon Interface Card for railiance-fabric.
+2. Export current entity categories and map them to canon anchors.
+3. Export current edge types and split them into canonical relationships,
+   candidate relationships, and display-only graph edges.
+4. Add evidence state to captured nodes and edges.
+5. Implement or document clean graph examples and bad-shape corrections.
+6. Record purpose fit, scope pressure, and requested canon evolution.
+
+## Expected Outputs
+
+- completed interface card,
+- entity capture mapping,
+- edge capture mapping,
+- display-only edge inventory,
+- evidence-state inventory,
+- visualization examples,
+- list of railiance-fabric refactor tasks,
+- list of canon evolution requests.
+
+## Non-Goals
+
+- Do not choose UI or graph database technology from this canon workplan.
+- Do not turn layout, color, cluster, or highlight metadata into canon meaning.
+- Do not change InfoTechCanon without a canon-side EvolutionRequest.