Architecture as executable context
Trace how purpose becomes policy, policy becomes structure, and structure becomes evidence-backed behavior. Every view on this page is generated from versioned repository truth.
Generated from repository truth · fingerprint e3d1991c555b
01Repository truth is canonical
02Dependencies remain explicit
03Generated views are disposable
System boundary
OptiFlow owns evidence and reviewable plans. Platform capabilities compose around it without leaking cloud or orchestration concerns into the domain.
The product turns opaque media collections into defensible evidence without treating detection as write permission.
Surrounding repositories add environment, delivery, and orchestration capabilities while remaining replaceable consumers.
Future mutation requires a separate transactional architecture with fresh evidence, explicit consent, validation, and recovery.
Structural model
Infrastructure implements explicit boundaries. Interfaces coordinate application use cases. Domain and evidence rules remain independent from deployment technology.
Owns command syntax, human and machine rendering, stream behavior, and operating-system outcomes.
clirendermainCoordinates use cases, interruption, configuration resolution, and immutable artifact commit boundaries.
appoutcomesignalsconfiguration::resolverOwns evidence language, policy values, inventory classification, exact relationships, and plan semantics.
domaininventoryduplicatesplanningOwns complete-content proof and the versioned boundary between domain values and public artifacts.
hashingcontractsschemasImplements filesystem, SQLite, external-adapter, and atomic artifact ports without defining domain meaning.
filesystemstatereportsadapters::ffprobeProjects repository truth into isolated static surfaces and assembles one collision-checked site artifact.
web/landingweb/architecturedocsscripts/siteArchitecture knowledge graph
The graph is generated from each document's depends_on metadata. Select a node to jump to its source contract.
Canonical corpus
Each document owns one kind of meaning. Filters change this projection only; the repository metadata remains the source of truth.
Why does the product exist, and what does it refuse to compromise?
Why does the product exist, and what does it refuse to compromise?
Why does the product exist, and what does it refuse to compromise?
Why does the product exist, and what does it refuse to compromise?
Why does the product exist, and what does it refuse to compromise?
What may the system claim, and what authority may an agent exercise?
Which concepts and human boundaries shape the product model?
Which concepts and human boundaries shape the product model?
What may the system claim, and what authority may an agent exercise?
How is meaning translated into systems, boundaries, decisions, and sequence?
How is meaning translated into systems, boundaries, decisions, and sequence?
How is meaning translated into systems, boundaries, decisions, and sequence?
How should interacting with OptiFlow feel and remain coherent?
How should interacting with OptiFlow feel and remain coherent?
How is meaning translated into systems, boundaries, decisions, and sequence?
How is meaning translated into systems, boundaries, decisions, and sequence?
How is meaning translated into systems, boundaries, decisions, and sequence?
How does the architecture system explain and govern itself?
Reusable publication contract
The build reads canonical frontmatter, resolves the dependency graph, combines repository-owned presentation configuration, and produces replaceable HTML and JSON projections.
/architecture/