Responsible agents in a flood of decorative certainty.
This is not a brochure. It is a front door, manifesto, and gamified hygiene surface for building against slop, self-righteous automation theater, and unverifiable system claims.
Practices
The conflict
The heedless sibling
Ships endless plausible filler, refactors what was not asked, mistakes volume for competence, and leaves you with the cleanup.
The obsessive guard
Hedges every sentence into vapor, asks for ceremony instead of judgment, and stalls useful work behind performative caution.
Manifesto
Specification before speed The hard part is deciding what the thing is. Fast code on a false premise is a more expensive mistake.
Provenance or it did not happen Repo, branch, commit, generator, and recoverable session trail belong on the artifact, not in somebody’s memory.
Carry over what matters Pin the load-bearing state. Let the decorative residue fall away on purpose.
Build before believing If it has not run end to end on real data and real routes, it is still a story.
Human stewardship over agent theater A user is not a passive consumer of model output. The system should make good stewardship easier.
one canonical runtime
sibling semantics
reviewed lifecycles
deterministic seams
landing page · manifesto · gamified mvp
Ship the discipline, not the delusion.
Solvulator should converge as a sibling system: legal ontology from
`lien` , health vocabulary from
`fleet` , vault contracts from
`gemini-gate` , provenance discipline from
`carryover` , deterministic scoring from
`solvulator-fevcm` , and one operator-grade runtime
spine in `hyle-sync/solvulator` .
Runtime Spine hyle-sync/solvulator
Human Gate review before dispatch
carryover provenance discipline
gemini-gate vault contract
FEvcm deterministic scoring
Signal Deck
Unverified drifter
No practices locked in yet. The system can still slide toward filler, theater, or undocumented state loss.
Live surfaces
Failure assumptions
- PWA install path may be absent; report it honestly.
- Service worker may be stale or refused; keep the app usable anyway.
- One green panel does not imply the legal data is normalized enough.
- Public ingress may fail while localhost works.
- A repo may have a branch and still not have a healthy remote.
- Responsible agents still drown if they cannot compact context and prove state.
Provenance