project-stateby Atomic47 Labs
Use cases

Where it earns its keep.

One foundation, four roles. Every use case below stands on the same base: your project’s history and documents, kept on an auditable timeline — citable sources, append-only, nothing overwritten. Ask it like an oracle, and the answer comes with receipts.

The foundation — project history & docs

Every document, decision, action, and signal lands on the timeline as it happens, with its source captured and citable. Nothing is ever overwritten; corrections are new entries. So the project can always answer the three questions that decide arguments, audits, and handoffs: what happened, what did we know at the time, and where’s the source? That’s the oracle. Everything below is built on it.

append-only · sourced · citable
CEO & exec

“Where are we, really?”

One live picture across every project — assembled from the tools and conversations your teams already work in, not from what people remember to roll up. Board packs and exec reports generate on cadence; hard questions get answers with sources; and the company’s intelligence stops living in individual heads.

The recognition: the board asks a hard question, and you ask the project, and it answers with sources.

Entrepreneur

“How do I keep the story straight while building the company?”

You’re wearing every hat — the investor update, the grant claim, the diligence binder all compete with the actual work. project-state collects the company’s history as it happens: decisions with reasoning, milestones with evidence, every claim citable to its source and date. Updates and claims generate themselves; you approve and send.

The recognition: diligence arrives, and the history is already there — timestamped, sourced, nothing to reconstruct.

Product owner & team

“Why did we build it this way?”

Decisions keep their context — who, why, what it depended on. Risks are re-assessed as new signal lands; drift between plan and reality surfaces early; status becomes a question to the oracle instead of a meeting. New teammates onboard by asking.

The recognition: “why is it like this?” gets an answer with a date and a source — six months later, from someone who wasn’t there.

Sales

“What did we promise, and what’s it worth?”

Every pursuit runs as governed intelligence: signals from calls, email, and Slack collected against the deal; commitments on the record; outbound comms queued for approval. Pursuit desks get the tender plugin — qualification with cited evidence, bid/no-bid as a decision with reasoning, six stages from discovered to closed. Win, and delivery starts with the entire history of what was said.

The recognition: the handoff carries everything ever promised to the customer — nothing lives only in the rep’s head.

Whatever the role, the reporting regime is yours by configuration — funders, boards, SR&ED, client services — packs, not custom development.