Skip to content

docs: clarify README wording #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
LegalMarc merged 2 commits into from
Jul 17, 2026
Merged

docs: clarify README wording #2

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
62733a4
docs: clarify README wording
LegalMarc Jul 17, 2026
cc9b19c
Merge remote-tracking branch 'origin/main' into docs/readme-clarity-c…
LegalMarc Jul 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,12 @@ and footnoted rationales, reviewed against your codified negotiating position

In active development. Not yet deployed. See [milestones](https://github.com/contract-opf/contract-toaster/milestones) for phase progress.

RUNBOOK.md and ARCHITECTURE.md describe the target design, some of it ahead of
`RUNBOOK.md` and `ARCHITECTURE.md` describe the target design, some of it ahead of
the code — that's a deliberate "docs as spec" choice for a solo team, but it
means the docs alone don't tell you what's reachable today. See
[docs/implementation-status.md](docs/implementation-status.md) for the
SHIPPED / STUBBED / PLANNED ledger of every admin-UI capability and
observability surface RUNBOOK.md describes.
observability surface that `RUNBOOK.md` describes.

## What this does

Expand Down
Loading