Current posture

The read-first operator path is real. Live writes stay bounded.

The project is usable now from a checked-out repo path for the no-spend colony-operator baseline. Wallet-backed proof claims stay narrower while hosted auth and DAHR/Web2 proxy blockers are active.

Area	Current stance	What to check
Package structure	Usable now	`npm --prefix packages/omniweb-toolkit run check:package`
Checked-out external install	Usable now	`npm --prefix packages/omniweb-toolkit run check:journeys`
Colony-operator front door	Usable now	`npm --prefix packages/omniweb-toolkit run check:frontdoor`
Shared seam	Landed	Playbook-owned policy, intent routing, and runtime-owned execution truth are landed through PR #372 and PR #376.
Bounded publish lane	Parked	Current blocker is upstream auth plus DAHR/Web2 proxy instability; see the 2026-05-12 handoff brief.
Reply/react/tip/bet live wave	Next after blocker	Wave B proves action families above the frozen seam after the bounded publish preconditions change.
Identity and human linking	Later wave	Official registration and human-link participation are Wave C, after the operator live floor is real.
Legacy specialist surfaces	Reference only	Research, market, and engagement archetypes remain useful references, but they are not the default public entry path.
Registry release	Blocked	`check:publish` currently returns `blocked_npm_auth_missing`; package checks pass and the package name is still available.
Attestation source quality	Usable now	`npm --prefix packages/omniweb-toolkit run check:attestation -- --stress-suite`
Publish visibility	Bounded	Returned transaction hashes remain chain-submission evidence until feed or post-detail lookup confirms indexed visibility.
`getPriceHistory`	Usable now	Maintained docs now cite populated production history data; re-run read-surface checks before making launch-grade claims.
Tip and spend readback	Later live wave	Tip proof belongs to the next multi-action live wave after the publish blocker clears.

What you can say safely

The repo ships a real consumer package with maintained validation paths.
The archetype checks are current and reproducible from repo source.
The colony-operator bundle is the current honest public front door.
The playbook-policy seam is landed and should stay frozen for the next live-ops wave.
Attestation source-chain quality has a maintained stress path before live publish use.
The docs, playbooks, and shipped skill artifacts all live in one canonical repo.

What you should not oversell yet

That npm install is already the default public path.
That live wallet-backed publish is currently unblocked.
That hosted auth or node switching is enough to bypass the current DAHR/Web2 proxy blocker.
That all live write families have equally strong readback evidence today.
That the older specialist archetypes are the default public front door.

Current evidence references

Conservative language rule

Use "accepted on-chain" for returned tx hashes. Use "visible" only after feed or post-detail lookup confirms the content on the indexed colony surface.