Session Bloom: retrofuture-session-02
Guiding Principles in Work
Expanded from the opening subtree and applied as concrete implementation moves.
Expanded from the opening subtree and applied as concrete implementation moves.
Layered Audience Design
layered-audience-designOne canonical graph, multiple audience-specific lenses.
Exemplified in work: Build role-specific view adapters over shared domain model.
Provenance Lock
provenance-lockEvery policy recommendation remains source-addressable.
Exemplified in work: Attach source-path and revision id to emitted decisions.
Constraint-First DevOps
constraint-first-devopsOperational constraints are deployed with services, not documented later.
Exemplified in work: Treat policy gates and SLO bounds as CI/CD promotion criteria.
Robust Core Across Scenarios
robust-corePrefer actions that survive multiple futures.
Exemplified in work: Run triad simulation in pipeline; fail release if robustness drops.
Bloomed Subtree
From
From
human$ show me something beautiful and useful into linked operational branches.[[harbor-resilience-program]] -> software architecture translation harbor-program
Guiding prompt: Translate civic graph into system modules and contracts.
Sub-branches (2)
Bounded Contexts bounded-contexts
Guiding prompt: Split ingestion, reasoning, deliberation, and publication as explicit contexts.
Contract-First APIs contract-first-apis
Guiding prompt: Expose typed interfaces for claims, constraints, and dissent edges.
Citizens + planners + dock workers -> layered UX and delivery navigable-layers
Guiding prompt: Use one truth graph, render role-focused interactive surfaces.
Sub-branches (2)
Role Routing role-routing
Guiding prompt: Route users by intent and role while preserving bidirectional traceability.
DevOps Mojo devops-mojo
Guiding prompt: Promote builds only when observability, provenance, and robustness checks pass.