docs band migration: merge 48 docs, trim 43 files #132

Open
opened 2026-08-16 06:59:41 +00:00 by coilyco-ops · 1 comment
Member

This repo declares the small documentation band, so its caps are
40 lines / 3,000 chars per Markdown file and 20 docs/*.md.

Measured by running the validator against this checkout:

  • docs/: 68 files against a 20 cap - 48 to merge away
  • 43 files over a size cap - 43 docs/*.md prose

The work

  1. Merge docs/ from 68 pages down to 20. Related pages join; a page that only exists because another got too long goes back where it came from.
  2. Bring 43 files under 40 lines / 3,000 chars. Breakdown: 43 docs/*.md prose.

Merging is the move, not splitting. Splitting one over-long doc into two trades
a size violation for a count violation, which is the whole reason the count cap
exists.

Done means

pre-commit run --all-files green, with no new entry under
[tool.agentic-os.documentation-layout] excludes. Excludes still govern
placement and flatness and no longer reach either size cap or the count, so
adding one cannot close this issue. A generated file over the cap is a
generator emitting too much, and the fix is the generator.

Take as long as it needs. There is no partial-credit state to reach for.

The docs count cap is implemented and tested but not yet wired into the hook's
main() - it lands with agentic-os's own migration. So pre-commit will not
fail on the count today. Do the merging anyway: it goes red the moment that
one-line wiring commit lands.

Parent: coilyco-flight-deck/agentic-os#1102. Rationale and the measurements behind the numbers:
docs/documentation-bands.md.

This repo declares the **`small`** documentation band, so its caps are **40 lines / 3,000 chars** per Markdown file and **20 `docs/*.md`**. Measured by running the validator against this checkout: * **`docs/`: 68 files against a 20 cap** - **48 to merge away** * **43 files over a size cap** - 43 `docs/*.md` prose ## The work 1. Merge `docs/` from 68 pages down to 20. Related pages join; a page that only exists because another got too long goes back where it came from. 2. Bring 43 files under 40 lines / 3,000 chars. Breakdown: 43 `docs/*.md` prose. Merging is the move, not splitting. Splitting one over-long doc into two trades a size violation for a count violation, which is the whole reason the count cap exists. ## Done means `pre-commit run --all-files` green, with no new entry under `[tool.agentic-os.documentation-layout] excludes`. Excludes still govern placement and flatness and no longer reach either size cap or the count, so adding one cannot close this issue. A generated file over the cap is a generator emitting too much, and the fix is the generator. Take as long as it needs. There is no partial-credit state to reach for. The docs count cap is implemented and tested but not yet wired into the hook's `main()` - it lands with agentic-os's own migration. So `pre-commit` will not fail on the count today. Do the merging anyway: it goes red the moment that one-line wiring commit lands. Parent: coilyco-flight-deck/agentic-os#1102. Rationale and the measurements behind the numbers: [docs/documentation-bands.md](https://forgejo.coilysiren.me/coilyco-flight-deck/agentic-os/src/branch/main/docs/documentation-bands.md).
Author
Member

Duplicate of #133, or rather #133 duplicates this one. Both describe the same migration for this repo - docs/ at 68 files against the small-band cap of 20, and 43 files over the per-file cap - filed a day apart, 2026-08-16 and 2026-08-17. #133 carries the extra measurement worth keeping, that merging costs about 3.7 lines per fold, so if only one survives it should probably be that one with this issue's framing folded in.

Duplicate of #133, or rather #133 duplicates this one. Both describe the same migration for this repo - `docs/` at 68 files against the small-band cap of 20, and 43 files over the per-file cap - filed a day apart, 2026-08-16 and 2026-08-17. #133 carries the extra measurement worth keeping, that merging costs about 3.7 lines per fold, so if only one survives it should probably be that one with this issue's framing folded in.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-proxy#132
No description provided.