Skip to content

docs: remove agent-partition build notes, honest backend status, claims-consistency with LIMITS#108

Merged
abrichr merged 1 commit into
mainfrom
docs/review-cleanup
Jul 14, 2026
Merged

docs: remove agent-partition build notes, honest backend status, claims-consistency with LIMITS#108
abrichr merged 1 commit into
mainfrom
docs/review-cleanup

Conversation

@abrichr

@abrichr abrichr commented Jul 14, 2026

Copy link
Copy Markdown
Member

Fixes documentation issues surfaced by external review. Docs only — no code, CI, openadapt_flow/**, or deploy/** touched.

What changed

1. Removed multi-agent build scaffolding from DESIGN.md

  • Deleted the "Module ownership (build phase — do not edit files outside your area)" table that assigned files to Agent A / B / C / D, plus the (Agent A/B/C/D) header suffixes and the leftover "by the integrator" build-role phrasing. Replaced the table with a plain module map. This orchestration scaffolding did not belong in a public design doc.

2. Honest backend status (DESIGN.md + README.md)

Previously both docs described native/RDP backends as "future adapters" / "exercised against mocked servers in CI — adapters, not rewrites", blurring very different maturity levels. Now stated plainly:

  • Browser is the shipped path, the only one proven end to end on a real third-party app.
  • WindowsBackend (UIA) is proven structurally on a local Windows-on-ARM VM (record → compile → replay, DB-judged).
  • RDP + Citrix are spikes, not validated integrations. The Citrix work is a pixel-only remote-display analog spike, NOT a validated Citrix integration, with the deferred gaps named: HDX compression/latency, ICA DPI & coordinate mapping, synthetic-input acceptance, lock/credential screens, no independent effect verification, unmeasured identity over-halt rate.

3. Reconciled stale version/maturity claims

  • README.md Status: replaced "v0 for the reference browser backend" (package is now 1.1.0) with honest uneven-maturity framing; flagged the Phase-2 workflow-program IR as prototyped against synthetic fixtures — experimental, not production.
  • docs/ECOSYSTEM_INTEGRATION.md: dropped stale "flow ships v0.3.0" and v0.3/v0.4 pins.

4. Claims-consistency with LIMITS.md (README now matches)

  • (a) Identity checks only protect armed steps; bundles arm a subset of clicks (live OpenEMR: 4-7 of 12) — an unarmed click has no identity check.
  • (b) Certification is optional/opt-in; the safe claim is "a certified workflow can be configured to halt", not "always halts".
  • (c) Effect verification needs a declared effect contract and a configured verifier; the compiler does not auto-infer effects.
  • (d) Template screenshots are not yet sealed inside the opt-in AEAD bundle container — they rely on operator full-disk encryption.

Verification

scripts/check_consistency.py passes (version, paths, phrases, test count).

Do not merge — awaiting review.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CKrVJJy5jWVCkXAqgUqtqZ

…ms-consistency with LIMITS

DESIGN.md
- Remove the "Module ownership (build phase)" Agent A/B/C/D file-assignment
  table and de-agentify section headers and the test-policy note (leftover
  multi-agent orchestration scaffolding not fit for a public design doc).
- Rewrite the backend-status intro: browser is the shipped/proven path; the
  Windows UIA backend is proven structurally on a local VM; RDP and Citrix
  pixel-only backends are spikes, not validated integrations.

README.md
- Backend status: stop lumping WindowsBackend + RDP as "adapters exercised in
  CI". State honestly that browser is shipped, Windows is VM-proven, and the
  Citrix work is a pixel-only remote-display analog spike (NOT a validated
  Citrix integration) with named deferred gaps: HDX latency, ICA DPI/coordinate
  mapping, synthetic-input acceptance, lock/credential screens, no independent
  effect verification, unmeasured identity over-halt rate.
- Claims-consistency with LIMITS: identity only covers armed steps (bundles arm
  a subset of clicks); certification is optional (a certified workflow can be
  configured to halt, not "always halts"); effect verification needs a declared
  effect contract + configured verifier and the compiler does not auto-infer
  effects; template screenshots are not yet sealed in the encrypted bundle
  container (rely on FDE).
- Status: replace stale "v0 for the reference browser backend" with honest,
  uneven-maturity framing; flag Phase-2 IR as synthetic-fixture prototype,
  experimental not production.

docs/ECOSYSTEM_INTEGRATION.md
- Drop stale "flow ships v0.3.0" / v0.3/v0.4 version pins and the "by the
  integrator" build-phase phrasing.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CKrVJJy5jWVCkXAqgUqtqZ
@abrichr abrichr merged commit 4e073cb into main Jul 14, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant