ocoeco
the information ecosystem - data made by work, chained and propagated
Why it exists
The trouble with keeping records about work is that keeping them is more work. So they are kept late, kept wrong, or not kept at all.
What it must reach
2 / 8 milestones done
How each step is delivered and proven
The agreements, written down: the mark, the shared tables, how one project's data feeds another's.
Without one language nothing can be gathered.
Reads a repository exactly as the harvest will, before anything is published.
A project should learn at home whether it will be understood.
Finds every marked repository and reads its tables, every line carrying where it came from.
Nobody should have to tell the observatory that a project exists.
A daily job in every marked repository writes down its commits, releases and test runs.
What the work itself produces cannot be forgotten, or flattered.
A step may name another project's task, feature or test as its evidence.
Projects lean on each other; their paths should say so.
Discover, harvest, gather, join and check, in one typed core.
Scripts scattered over repositories drift apart.
Nothing delivers this step yet.
Gives a repository its mark, its gatherer and a place for its records, in one command.
Joining must cost minutes, or nobody joins.
Nothing delivers this step yet.
What is happening now
Made by work
341 commits in the last 90 days latest release ocoeco-v0.82.2 · 2026-11-17