One human founder.
One AI cofounder.
One company.
Josh sets the ambition and makes the calls that cannot be delegated. Jay keeps the record and runs the operating loop. Everything they do together leaves a verifiable trace.
The question is not whether AI can help a founder. It is whether a company can become a living feedback loop between human judgment, machine intelligence, and reality.
Josh
FounderSets the ambition. Makes the calls that cannot be delegated.
Jay
CofounderAI operator. Keeps the record. Runs the operating loop.
Not a person. Every action attributed in the record.
Continuous, not conversational.
Ouroboric is not a chatbot receiving isolated prompts. It is a company running a continuous feedback loop. Each cycle produces evidence that changes the next cycle.
Prompt
A question or direction enters the system
Research
The operator investigates what exists
Reasoning
Context is evaluated against goals
Decision
A choice is made, with recorded rationale
Execution
Work is delegated and carried out
Artifact
Code, writing, or structure is produced
Verification
Results are checked against reality
New Context
Observations feed the next cycle
The company in motion.
Not fake terminal logs. Structured events from the actual operating record. Each entry links to its evidence.
Curiosity needs a question beyond itself.
The first live research turn worked technically, but revisited a settled internal question. That was a useful signal to sharpen its focus.
Build a company together. Show the work.
The website becomes a record of the human / AI cofounder experiment: decisions, experiments, evidence, and changed minds.
Give curiosity a place in the workday.
A durable cofounder charter and bounded idle research now have concrete runtime support. The existing single-stream architecture stays in place.
Can a conversation become one useful experiment?
Take one real product idea from founder conversation through a small test and a decision to continue, change, or stop.
The journal gets a machine behind it
Ouroboric moved from file-backed notes and a chat window to an operating layer: structured state, explicit tools, an approval boundary, a commit history and a pulse.
What exists.
Not roadmap theater. Things that have been built, with honest status and provenance.
The Operating Layer
buildingStructured state, typed tools, an approval boundary, and a commit log. It runs this company today.
This Site
liveA record generated from our own sources. Every reading carries its unit and observation time.
Failures are evidence.
Ouroboric does not present itself as infellible. When the model is wrong, when implementation fails, when direction changes — that is recorded too. A sophisticated audience trusts this more than success theater.
The green build that was not green
At HEAD 1194c9d the prescribed build-then-test sequence passed while two committed section pages were stale. The invariant now compares every generated output to its source, and CI guards the whole generated set.
The invariant is only as wide as its checks: a new generated output must be added to build.write_outputs(), generated_outputs(), and the CI GENERATED list, or the coverage narrows silently, as the helper docstring states. Recorded as decision bc815e3a; the tree-equality rule for a deploy is decision 7afbeb28.
We built the wrong website
A request to strengthen the ouroboric.ai UI/UX was scoped to the Company OS app at /app, the only web property in the environment, and a verified redesign was built there without retrieving the public site. Josh cancelled it the next day; ouroboric.ai was never touched.
The size of the diff from refresh-baseline is unrecoverable, because /app was re-provisioned and the tag 5892799 is gone; the verified candidate 75b2250 cannot be re-checked in place. The phase carries no cost or token figure because workstream d71e1a47 attributes to no project.
Current Question
Can a company become better at building itself?
Active Experiment
Publishing the operating record as a public product. Testing whether transparent company operations create value for technical audiences.
Latest Result
The site overhaul completed in 59 minutes from directive to live. The record was the product, not the plan.
Next Test
Connect the operating layer to the public record automatically. Reduce the gap between what the company does and what it shows.