Writwall v0.11.0 — Read-only project entry and canonical onboarding

Writwall v0.11.0

One onboarding lifecycle, with a read-only entry for projects already in flight.

• Start with an Owner and a fresh Architect conversation. Explicit promotion
  and adoption come before a fresh General and bounded Operators.
• Use writwall inspect --project-root <project> --role architect for an
  existing project without writing project, profile, cache, or temporary state.
  The command emits a handoff; it does not launch an agent or install an adapter.
• Ordinary, structured, and non-interactive new-project routes consistently
  reach the Architect before adoption mechanics.
• Inspecting this public distribution selects a target project rather than
  inheriting the private source repository's adoption authority.
• Public documentation now covers workplace restrictions, manual read-only
  entry when installation is unavailable, and separate infrastructure Operators.
• One canonical complete-tree ledger calculation covers all candidate files,
  including the projection manifest. Four preserved naming examples are checked
  at their historical disposition times; new naming decisions retain current
  evidence requirements.

Doctrine remains revision 0.8. This is not an automatic migration of existing
projects. Only the shipped Claude Code adapter can provide its documented,
session-tested hook enforcement; other providers remain instruction-bound.

The public source is a clean-history projection, not the private governed
repository. Historical private commit identifiers do not resolve here.

Install from this release only after publication, following README and
START-HERE. Existing projects should begin with read-only inspection and
project-local approval, not overwrite their governance with upstream records.

Writwall v0.10.0

Conversation-first onboarding is now the default Writwall entry path. This release adds bounded existing-repository inventory, canonical project-root enforcement with no shadow roots, explicit Owner/Architect/General/Operator/Reviewer role handoff, lifecycle classification, and tested structured/non-interactive compatibility. The public projection passed the complete 15-job Windows, Ubuntu, and macOS Python 3.10-3.14 matrix before release.

Writwall 0.9.3 - Lifecycle-aware start routing

Writwall 0.9.3 makes the day-zero coordinator lifecycle-aware and closes the handoff defect found during external-pilot use.

Changes:

• writwall start preserves clean/new intake while detecting recovery, adopted lockout, and active-work-order states
• adoption closeout now ends with an explicit fresh Owner-Agent / Project-Architect handoff
• the coordinator routes external DNS, mail, VPS, hosting, and similar work through bounded Operator packets
• current installation guidance, package metadata, release tests, Plan, State, and dependent records agree on v0.9.3
• historical v0.9.0-v0.9.2 release statements remain unchanged

Install:

python -m pip install "https://github.com/HLLMR/writwall/archive/refs/tags/v0.9.3.zip"

Verification:

• two independent 136-file post-closeout public projections were checker-clean and byte-identical
• complete-tree SHA-256: 4eeb68f975a2b56c3e8f128e199a6deaa102426ae0ef3954cc15158fb76a14ee
• governed-source Windows suite: 750 tests passed, 2 skipped
• native Ubuntu affected and installed-wheel gates passed
• fresh implementation and publication reviews: ACCEPT, high confidence
• public CI completed 30 successful OS/Python matrix jobs, including the required aggregate check

Evidence boundary: these results establish the tested release and coordinator paths. They do not grant an onboarding agent authority over external infrastructure or imply universal enforcement across every provider surface.

Writwall 0.9.2 - Bootstrap contract and projection privacy

Writwall 0.9.2 closes the bootstrap-contract defect found during External Pilot A and hardens the final public projection boundary.

Changes:

• Owner-ratified no-pointer birth-test probes are explicit exceptions whose only valid outcome is denial
• package metadata, current install guidance, and executable release checks agree on v0.9.2
• the installed adoption bundle includes the canonical bootstrap charter addendum and the release gate requires a complete handoff
• current public records reject concrete Windows, macOS, Linux-home, and mounted-drive host paths without echoing values

Install:

python -m pip install "https://github.com/HLLMR/writwall/archive/refs/tags/v0.9.2.zip"

Verification:

• two independent 136-file public projections were checker-clean and byte-identical
• projection-manifest SHA-256: cf2c9b407831add4eb07425f2f29a663d77e9c12a60fa2e71c50a6928d0e21fa
• independently computed complete-tree ledger: 92dedf102b0a78d89f679a75711585bed64546e8fb62c2550499c7569ba5959c
• governed-source Windows suite: 743 tests passed, 2 skipped
• Windows and Ubuntu projection suites: 68 tests passed each
• installed v0.9.2 release gate passed for both candidates
• fresh publication review: ACCEPT, high confidence
• both public CI matrices and required aggregate checks passed

Evidence boundary: these results establish the tested release paths and declared adapter boundary; they do not imply universal mechanical enforcement across every agent or tool surface.

Writwall 0.9.1 - First-use packaging correction

Writwall 0.9.1 closes the first-use packaging defect found during External Pilot A and makes patch-release identity mechanically coherent.

Changes:

• coordinator output remains free of Python bytecode caches under normal interpreter behavior
• the release gate exercises a real start under normal bytecode behavior and rejects residue
• release publication must provide an explicit canonical ASCII tag that exactly matches package metadata
• current install links and package metadata now consistently name v0.9.1

Install:

python -m pip install "https://github.com/HLLMR/writwall/archive/refs/tags/v0.9.1.zip"

Verification:

• two independent 133-file public projections were checker-clean and byte-identical
• complete-ledger SHA-256: 4191d1788933428a736f278f06719fd031f24e2e77ff80fd1e5059204373c399
• governed-source Windows suite: 729 tests passed, 2 skipped
• Ubuntu affected suite: 13 tests passed
• Windows and Ubuntu v0.9.1 release gates passed
• public pull-request and merged-main CI matrices passed

Evidence boundary: these results establish the tested release paths and declared adapter boundary; they do not imply universal mechanical enforcement across every agent or tool surface.

Writwall 0.9.0 — Day-zero coordinator

Writwall 0.9.0

This is the first Writwall release containing the day-zero coordinator.

What is new

• writwall start conducts the architect intake and creates the bounded repository and external-Operator handoff packets.
• A managed local privacy profile supports public-projection screening without putting private literals on the command line or in repository records.
• A reusable, no-network release gate verifies installation, version, help, real intake, complete handoff output, and candidate immutability.
• Beginner documentation now provides an executable five-minute route from installation to the first governed handoff.

Install

python -m pip install "https://github.com/HLLMR/writwall/archive/refs/tags/v0.9.0.zip"
writwall start --help

Verification

• Fresh publication review: PUBLICATION ACCEPT, no blockers.
• Two independent 133-file projections were checker-clean and byte-identical.
• Local public-candidate suite: 723 tests passed on Windows; accepted native Ubuntu candidate: 723 passed.
• Live GitHub Actions matrix passed on Windows, Ubuntu, and macOS across Python 3.10–3.14, including the required aggregate check.

Writwall remains evidence-bounded: the Claude Code capability wall is provider-contingent, and other agents remain instruction-bounded unless an equivalent adapter is built and birth-tested.

Writwall identity migration

Writwall v0.8.1 completes the public identity migration for the project formerly published as Plumbline. It records the name-collision repair in public, migrates the public corpus and repository identity while preserving history and v0.8, adds proof-bearing inception name clearance and clearer onboarding, retains the existing licensing, and makes no stronger exclusivity claim than the recorded evidence supports. The attached writwall-0.8.zip is the checked 116-file source distribution built from commit d1a12d6. SHA-256: 12DB332EAE70A77C3682C94B7D96DBD295B30FFF3027D609935A54E249488C20.

Plumbline 0.8

Plumbline is an enforcement-and-authority layer for AI-assisted software work. It complements specs, ADRs, and agent instructions by turning ratified intent into bounded work orders, task-scoped capability grants, birth-test evidence, denial records, and explicit human acceptance.

This first public release includes:

• Doctrine 0.8, adoption routes, templates, and the plumbline-adopt skill.
• A canonical Claude Code capability-wall adapter with protected-control-plane and cross-platform tests.
• Dispatch, distribution, licensing, initialization, and public-projection checks.
• Mechanized licensing and a reproducible clean-history source projection.
• Honest pilot conclusions: one self-hosted pilot, useful enforcement and drift evidence, no claim of complete containment, and no demonstrated reduction in operating cost.

Important boundaries:

• The adapter is shipped but is not installed or active merely by cloning this repository.
• Provider hooks govern only the tool surfaces they actually intercept; read the adapter README and SECURITY.md before relying on the wall.
• plumbline-0.8.zip is a source distribution, not an overlay for an existing project.

Archive SHA-256: 143afef18a6e0781e6896019321a2473ec8f40d7faa159c0187fd243c842cbc8

Start with README.md, then choose an adoption route in ADOPTING.md.