mikoshi-constructA repository that already knows how it is built

Architecture policy, an API contract, a quality harness and agent instructions — materialized into a repository in one command, then kept honest by a tool that says "unknown" when it cannot prove otherwise.

Getting started

The development cycle

CLI reference

One command, a working baseline
An empty directory or a repository with ten years of history. Policy, harness, contract and agent instructions land; nothing you wrote is overwritten, and there is no --force.
The harness decides, not the agent
Every implementation runs at the lowest reasoning class that can carry it, and a separate verifier — never the implementer — runs the quality gate and reports whether a test was weakened.
Discovery instead of guessing
The CLI reports facts only. Everything that needs judgement is a marked block the coding agent fills by reading the code, with provenance recorded in the manifest.
Claims graded, never assumed
doctor reports an enforcement level from L0 to L3 with the evidence it read, and answers "unknown" where proving a thing would mean running it.
Upgrades you can read first
construct sync replays today's templates against the record the manifest cut at init, classifies every path, and writes only what it can prove the construct owns.
A record that is never crossed out
construct.json is the protocol of everything the construct has written here. No run rewrites another run's lines, and every replacement is printed rather than performed quietly.

mikoshi-constructA repository that already knows how it is built

One command, a working baseline

The harness decides, not the agent

Discovery instead of guessing

Claims graded, never assumed

Upgrades you can read first

A record that is never crossed out