Progress - Source Excerpt 03 - Next Maintenance
Summary
This source excerpt begins near Next Maintenance and preserves the surrounding evidence from 2IA.org/.uai/progress.uai.
**Source path:** 2IA.org/.uai/progress.uai
- Same-day editorial correction after owner review: the generated detail-page opening was too self-referential and read like process filler. The `Fast Brief` now uses concrete labels (`What is broken`, `Who benefits`, `Who gets hurt`, `Do this first`, `Document to pull`) and route copy now names government procurement, court pressure, private dossiers, records delay, automated suspicion, and specific documents to pull. The homepage and Research Archive gained a `What is actually broken` / system-failures layer covering government, justice, economy, records, algorithms, and a direct call to pick one local machine and put it on the record.
- Follow-up owner correction on 2026-05-17 moved "how this route was assembled" material out of prime Research Archive real estate and into a small bottom help/source-notes disclosure. The detail generator no longer requires or renders old process sections such as `Where The Pressure Shows Up`, `What A Stronger Public Record Would Show`, `Reader Payoff`, or `Public Questions`; it now renders `The Failure`, `What To Demand`, `The Record Trail`, and `What Would Prove Us Wrong`.
- The route manifest and regression test were recalibrated away from enforced word-count bloat: the detail target is no longer an 8,000-character hard gate, and the test now protects concrete failure/demand labels instead of rewarding template volume. Live verification on `http://localhost:8904/` passed all 86 routes after the bloat reduction; the Agent File Handoff audit reported all active workspace intake buckets clear.
- A five-report Who Cares Wizard Improvement batch was processed on 2026-05-17 and archived under `agent-file-handoff/Archive/2026-05-17-who-cares-wizard/`. The homepage now includes a local-only `Who Cares Wizard` that asks for issue type, user goal, urgency, and evidence, then produces a pressure map with who can act, what is broken, records to pull, a written demand, boundaries, internal 2IA links, and external places to check. The tool does not submit data, create an account, or act as a secure drop, legal hotline, or crisis service.
- A ten-report organizations/resource-directory Improvement batch was processed on 2026-05-17 and archived under `agent-file-handoff/Archive/2026-05-17-organizations-directory-overhaul/`. The site now has a source-controlled `/organizations/` route with 11 detail dossiers, directory fields, starter sets to verify, Alabama starter coverage, civil-liberties/OSINT/AI-governance/digital-rights/public-records resource framing, high-risk historical hacktivist-entry boundaries, and 2IA name-collision disambiguation. The homepage Operating Desk, fallback navigation, JSON-LD schema, SEO matrix, and route manifest were updated.
- Verification after the organizations-directory pass: `tools/Test-2IAContentRoutes.ps1 -StaticOnly` passed for 98 manifest routes; Studio WordPress eval returned `25` virtual pages and confirmed `/organizations/` has 11 sections; Studio render smoke produced the Organizations route and a generated detail route with 7 external verification resources. Standalone `php` is still unavailable on PATH. Live HTTP checks against `http://localhost:8904/organizations/` timed out, so full live crawl was not run in this pass.
- On 2026-05-18, the top-navigation/header-copy/homepage-density intake was processed after owner feedback that public pages were showing internal instructions and the hero wasted space. The homepage hero now fills the right rail with the visual, `First records to pull`, and copyable argument panels; public copy no longer renders scaffolding such as launch drafts, SEO/internal-link labels, route compatibility, source-note boundary labels, or repeated route questions. `tools/Test-2IAContentRoutes.ps1` now blocks those phrases in rendered public text and requires distinct accountability questions.
- Verification for the 2026-05-18 pass: static route regression passed for 151 manifest routes; Playwright desktop/mobile homepage screenshots confirmed the right rail is populated and mobile stacks cleanly; targeted live public-phrase smoke passed for About, Research, and Research Archive pages. A full live crawl initially exposed stale `Publication boundary` copy and a duplicate Research question; both were fixed. Standalone `php` remains unavailable on PATH.
## Next Maintenance
- Keep `.uai/progress.uai` current when durable project state changes.
- Keep `.uai/decisions.uai` current when architecture, ownership, support-boundary, or packaging decisions change.
- Re-run PHP lint when PHP is available after PHP edits.
- Run `tools/Test-2IAContentRoutes.ps1 -BaseUrl <local site URL>` before release packaging or after public route edits.
- Use `tools/Test-2IAContentRoutes.ps1 -StaticOnly` when a WordPress server is not running; it checks manifest coverage and source-controlled required phrases without HTTP.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived 2026-05-16 batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-16-lawful-intelligence-improvement` batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-16-osint-anonymous-improvement` batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-16-home-psychological-warfare-improvement` batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-16-publication-system-improvement` batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-16-publication-system-followup` duplicate-context batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-17-civil-liberties-overhaul` batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-17-organizations-directory-overhaul` batch.
- Before release packaging, confirm active `Content/` and `Improvement/` buckets remain clear after the archived `2026-05-18-top-navigation-density-public-copy` batch.