I need to see what changed in the project
/repo-growthWhat works
Live tree, recency buckets, git drift, and snapshot capture.
Missing
No diff view yet; only structural recency and status.
agency engine
Worked Routes, Not A Landing Page
This root is an index into the parts of the app that already do something specific. Each case below names the route, what is actually proved there, and what is still missing.
If a route cannot answer a real user need yet, it should not be promoted here.
worked user cases
I need to understand how the app is put together
/application-structureWhat works
Request path, hot expressions, and brittle seams are spelled out in the running app.
Missing
Still no linked source lines or internal code browser.
I need one route that explains the bigger shape
/architectural-atlasWhat works
Themes, omissions, and pattern claims are tied back to live routes.
Missing
Some themes are still ahead of execution.
I need to inspect a semantic demo, not just read about it
/hydra-evaluatorWhat works
Hydra scenes are executable in-browser with camera input and explicit scene mapping.
Missing
No replay ledger or saved scene history yet.
I need internal operational status
/backofficeWhat works
Engagements, risks, and office health are visible in one route.
Missing
Data is mocked, not yet backed by a real ledger.
current state
Public subdomain
epistemic.hyperstitious.org is now serving the app
Validation
health endpoint, route checks, and repo-growth API are wired
Current weakness
the app is still one namespace and several routes are more articulate than operational
Next honest move
Split the server namespace, replace mocked backoffice data with a real file-backed ledger, and keep expanding only the routes that already answer a concrete need.
scope
Research Systems
Methodologically serious forecasting, uncertainty reduction, and decision surfaces tied to explicit datasets, baselines, and validation.
Operational Intelligence
State models, traces, backoffice reality, runtime truth, and validation harnesses that keep systems legible under pressure.
Product And Agency Surfaces
Landing pages, route families, internal doctrine, and client-facing artifacts bound back to the same operating core.
what this app is for
Research
Unit
uncertainty, dataset, baseline, method
Outcome
falsifiable work plan and sharper decision surface
Operations
Unit
state, trace, change, handoff
Outcome
clearer visibility into what changed and what to do next
Delivery
Unit
route family, ledger, runtime, proof surface
Outcome
public and internal surfaces served from one system without drifting apart