Changelog

Your impl docs now have two durable sections: UX (how it looks and feels) and Technology (how it gets built), with UX leading and Technology serving. Every detail discussed lands in the file, no filtering, so the coding agent has the full spec instead of half the context still in chat. Briefs lead with a DAG of atomic specs as the execution surface, and a new Build mode brackets plan mode with the open and close bookkeeping.

Osis now routes shared product knowledge (facts, principles, project state, ICP, brand) into your osis docs instead of Claude Code's per-user memory. Your context travels with the repo, so cofounders, hosted agents, and other surfaces see the same source of truth instead of single-tenant memory that never leaves your machine.

Open product threads that didn't land in a typed doc now get captured automatically as signals in your product inbox at conversation lulls or explicit cues. Unapplied thinking survives compaction and session breaks.

Iteration briefs now declare dependencies between phases inline. Independent phases execute in parallel instead of waiting on artificial ordering, and the agent reads the dependency graph to know what's safe to run concurrently.

Osis is now research-backed. Per-doc reasoning principles distilled from deep research into canonical product frameworks (JTBD, PR/FAQ, Loop, North Star, and more) drive the agent's drafting silently across every osis doc. Modules wrap activities like customer discovery as typed surfaces in osis.json alongside products. Protocol bumps to v2.0.

Osis now onboards by having a real conversation. It loads your repo as context, asks one sharp question tuned to your product, and captures your current thinking at the right altitude as you talk. No empty docs, no setup wizard.

Osis now reports pseudonymous activation, onboarding, and update events so we can measure traction without sending repo content or product names.

Osis now has a mark, a time-aware greeting, and new versions that ask before upgrading.

Every doc now tracks the agent sessions that built it — date, summary, and a resume command. See exactly who thought about a file and when.

Run osis across multi-product repos — each product gets its own specs and context.

The agent reads your product docs before the conversation starts. No re-explaining.

Digital twin, structured specs, signal processing, and drift detection.