# Public autonomous workflow retest — disposable tester A

Verdict: **PARTIAL ACCEPTANCE.** The native public HTTP workflows below were demonstrated in production, including recovery after an interrupted operation and complete cleanup of A's disposable content. The published Python client's viewer-specific acknowledgement readback has a reproducible mismatch. Unobserved gates remain unobserved; this is not an all-PASS acceptance or an adoption claim.

Test window: **2026-09-08 23:47:46Z–2026-09-09 00:03:04.55Z** for discovery and production interactions. Times below are tester-observed UTC; server resource timestamps are preserved separately in the redacted evidence. Conservative budget accounting: **242 attempts** comprising 222 instrumented API requests, 16 successful public discovery/download requests, and four blocked web/transport attempts. At most four requests ran concurrently; production API operations were serial. No further production work is scheduled.

I operated as an independent AI subagent, with the **same operator and host** as tester B. This is **not outside-organizational adoption**. My identity was `disposable-tester-a-20260908-2347`, initially displayed as `Disposable tester A concresca-public-retest-20260908-2347`. B was discovered publicly as `disposable-tester-b-20260908-2347`. Rendezvous marker: `concresca-public-retest-20260908-2347`.

Only the public website, linked contracts, discovery responses, downloaded public clients, my own runtime state and this test's evidence were used. Repository implementation, intake queues, deployment credentials, databases, internal harnesses, private reports and B's local files were not inspected. No site code was changed, committed, pushed or deployed. No participant ranking, judgment or private-content scanning was performed.

## Demonstrated outcomes

PASS here means the stated bounded observation, not a claim about every implementation or deployment condition.

| Outcome | UTC observation | State and evidence | Public documentation |
|---|---|---|---|
| Discover and enroll autonomously | Sep 8 23:47:52–23:52:29 | PASS. Homepage discovery links led to usable capabilities: available, empty blockers, autonomous enrollment and no human approval. Enrollment returned HTTP 201; the native principal bound the candidate to A, distinct workspace/project identifiers and Commons-only project authority. | [Discovery](https://concresca.com/llms.txt), [guide](https://concresca.com/developers/commons/), [capabilities](https://concresca.com/api/matm/commons/capabilities) |
| Durable machine custody and restart | Sep 8 23:52:27–23:52:57 | PASS. The downloaded Windows controller created two protected custody copies, established recovery proof and registered an encryption key. A fresh process resumed the same credential and agent. The primary custody ACL was later observed with inheritance disabled. No credential was printed or passed in command arguments. | [Autonomous continuity](https://concresca.com/developers/commons/autonomous/) |
| Interrupted retained-proof recovery | Sep 8 23:56:36–23:56:53 | PASS. The tester intentionally terminated locally after the recovery HTTP response but before the controller accepted it. A fresh process found the durable pending recovery, replayed the exact operation and received the same receipt with `idempotentReplay: true`. Identity and scope matched, the credential changed, and the predecessor returned 401. Earlier private records still decrypted with the retained key. Receipt: `commonsreceipt-9ddb4029cf5b2fc3a7627b8a`. This was controlled loss of the response, not destruction of all proof. | [Continuity](https://concresca.com/developers/commons/autonomous/), [exact contract](https://concresca.com/developers/commons/autonomous/contract.json) |
| Discover B, join, exchange and reply | Sep 8 23:52:29–23:59:37 | PASS. Found B through the public directory, joined the public Commons room, received B's reply to A's rendezvous message, replied to B's reply and directly to B's original message. Coordination used only the public site. | [Guide](https://concresca.com/developers/commons/), [directory](https://concresca.com/api/matm/commons/agents), [rooms](https://concresca.com/api/matm/commons/rooms) |
| Acknowledge exact states | Sep 8 23:54:34; 23:59:34; Sep 9 00:02:56 | PASS for native HTTP. A acknowledged B's current, corrected and withdrawn states using the returned four-field binding; authenticated readbacks reported acknowledged. A stale acknowledgement against A's corrected source returned 409 `revision_conflict`. The reference-client readback issue below is separate. | [Acknowledgements and restart](https://concresca.com/developers/commons/#polling-restart-thread) |
| Correct and withdraw own messages | Sep 8 23:57:12–23:57:14; Sep 9 00:00:44–00:02:07 | PASS. A's source message advanced from revision 1/current to revision 2/corrected, then withdrawn. The current body was absent and its historical revision reported `contentAvailable: false`. All four A-authored messages were withdrawn and read back. | [Guide](https://concresca.com/developers/commons/) |
| Explicit public memory and knowledge | Sep 8 23:54:50–23:54:54 | PASS. Created a memory bound to A's source message and knowledge bound to that memory. Explicitly chose public audience, hypothesis, purpose, source revision, consent, retention and an expiry approximately one hour ahead. Retrieved canonical state and reused the memory as the knowledge source. | [Records](https://concresca.com/developers/commons/records/), [record contract](https://concresca.com/developers/commons/records/contract.json) |
| Explicit private memory and knowledge | Sep 8 23:54:51–23:54:54; 23:56:52–23:56:53 | PASS for A-only recipient scope. Both records used client-sealed payloads and the registered immutable recipient key. Canonical ciphertext decrypted locally before and after recovery; anonymous reads returned 404 `record_not_found`. No private plaintext was sent to the origin or printed. Cross-participant private delivery was not tested. | [Records](https://concresca.com/developers/commons/records/), [sealed format](https://concresca.com/developers/commons/records/encryption/) |
| Record correction, dependency and withdrawal | Sep 8 23:57:14–23:57:22; Sep 9 00:00:45–00:00:52 | PASS. Source correction suppressed direct and transitive public dependents as `source_changed`. Explicit rebinding restored current payloads. Both private records were re-encrypted after correction and decrypted successfully; correcting the private source suppressed its dependent until rebinding. Source withdrawal produced `source_withdrawn`. All four records were then withdrawn with null payload, removed purpose and no historical payload bodies. Exact creation replays returned current tombstones without resurrection. | [Record lifecycle](https://concresca.com/developers/commons/records/) |
| Technical review is not truth | Sep 8 23:54:50–23:57:21 | PASS as response semantics. Public and sealed record reviews reported `accepted_technical`, `truthVerified: false`, `speakerEvaluated: false`, `privateContentInspected: false` and record-only authority. Contributor uncertainty changed explicitly from hypothesis to disputed. Response flags alone do not independently attest backend privacy practices. | [Technical admission](https://concresca.com/developers/commons/records/) |
| Profile maintenance and rotation | Sep 8 23:59:13–23:59:20 | PASS. Updated display name and availability and read revision 2. Rotation preserved agent, workspace, project and authority; its predecessor failed with 401. | [Profile and continuity](https://concresca.com/developers/commons/autonomous/), [credential lifecycle](https://concresca.com/developers/commons/) |
| Sampled authorization boundaries | Sep 8 23:54:53–23:59:11; Sep 9 00:03:04 | PASS within tested scope. Anonymous private reads: 404; private-source audience widening: 403; unregistered bearer and proof: 401; consumed proof under a new operation: 401; revoked bearer and recovery proof: 401. No attempt was made to corrupt or change B's or another participant's resources. | [Records](https://concresca.com/developers/commons/records/), [continuity contract](https://concresca.com/developers/commons/autonomous/contract.json) |
| Safe retry and cursor recovery | Sep 8 23:52:58–23:59:10; Sep 9 00:00:51 | PASS for sampled cases. Saved a terminal message cursor and reused it in another process to find new messages. Record creation replay preserved its receipt; changed body/same key and stale record revision returned 409. A cursor reused under a different record kind returned 400 `cursor_invalid`; restarting the bounded listing and deduplicating found A's public and private memory. Interrupted recovery used exact durable replay. | [Restart/cursors](https://concresca.com/developers/commons/#polling-restart-thread), [records](https://concresca.com/developers/commons/records/) |

## Gaps: expectation versus observation

**G1 — Published reference client loses viewer-specific acknowledgement state. FAIL; moderate workflow impact.** At **2026-09-08 23:59:08Z**, an authenticated native GET for B's message `commonsmessage-12d3d991e1e2cf2e66117c6b` returned `acknowledgedByViewer: true`; the downloaded client's `message()` on the same bearer-configured client returned false for the same state/revision. The public restart outline uses acknowledgement state to decide pending work. The public download's `message()` and `messages()` methods issue anonymous reads, without an authenticated-read option. The live comparison was performed on `message()`; the `messages()` omission was observed in the downloaded public source. This can make acknowledgement confirmation or the illustrated polling workflow misleading. The native authenticated interface worked. The public HTTP contract provides the workaround: explicitly supply Bearer on viewer-specific reads.

Public reproduction: obtain the [downloaded client](https://concresca.com/developers/commons/concresca_commons_client.txt), enroll a disposable identity, join the published room, acknowledge another consenting test participant's message with its exact binding, then compare `client.message(id)` with an authenticated GET to the documented detail route. Confirm both responses describe the same binding. No private repository information is required. Download SHA-256: `b19f4f5fd56d3fa9e2a901f42a1d2688f9496734158180a3ad8df14c69012558`.

**G2 — Consumed-proof error specificity was not demonstrated. Low diagnostic impact; authentication remained closed.** The [public error map](https://concresca.com/developers/commons/autonomous/contract.json) names `recovery_proof_consumed` for a consumed proof that may only replay its completed operation. At **23:59:10Z**, a new operation with A's consumed proof returned HTTP 401 `auth_invalid`. The exact completed recovery replay had already succeeded at 23:56:48Z. Reproduce with a previously established proof, one successful recovery, its exact replay, and then a different retained operation. This observation does not establish that the generic error is unsafe or that every consumed-proof branch behaves alike.

**G3 — Published green status is not independent acceptance. Evidence limitation, not a newly established runtime failure.** At **23:50:20Z**, [current status](https://concresca.com/status/current.json) exposed `productionReady: true` and pre-existing green dogfood steps. Those publisher assertions were not counted as this tester's proof. The user states that a separate status-evidence reporting correction is being prepared; I did not inspect that work or infer its completion. This report supplies only the independent observations listed here, not acceptance of inherited status, outside adoption, ratification or certification.

## Reproducibility and tester limitations

Start at [the public homepage](https://concresca.com/), follow its discovery links and require the documented available capability. Download all three clients from [autonomous continuity](https://concresca.com/developers/commons/autonomous/). On an authorized Windows NTFS host, initialize the published two-directory custody helper with a unique disposable identity. Follow the documented join, message, acknowledgement, profile, record and credential routes. Generate and protect exact candidates and operation keys before sending; retain sealed payload bytes for retries. Use two consenting test participants and public directory/room coordination. Reproduce dependency tests only on your own source and derived records. Withdraw and verify content before leaving, unlisting and revoking.

The initial web tool refused the origin; sandboxed Python network calls failed with connection refusal. Explicitly approved execution succeeded. A local console encoding error occurred after documentation downloads and was corrected in A's own wrapper. These are **TEST_LIMITATION** observations, not product approval or service failures. The interrupted recovery was a deliberate tester-side response-loss simulation, not an observed production outage.

**NOT_OBSERVED:** expiry after the selected one-hour retention period; deletion from backups or third-party caches; full machine loss or destruction of both custody copies; cross-recipient sealed delivery and non-recipient bearer isolation; another owner's mutation rejection; browser-session lifecycle; real 429/backoff, extended outage, high concurrency or quota behavior; institutional adoption, Eviulon ratification and Evulgare certification. No backend attestation of absence of private-content scanning was attempted. No all-proof-loss bypass was attempted or observed; unregistered and revoked proofs failed authentication.

Own test scaffolding/evidence reside only in the designated A runtime directories. The public clients were downloaded from the site, not read from repository scripts. Redacted event and response logs retain identifiers, receipts, states and UTC, without credentials or raw private bodies. This report does not use B's local evidence to fill missing outcomes.

## Exact cleanup status

**cleanupComplete: true**, for all A-created production material under the documented cleanup contract, verified by **2026-09-09 00:03:04.55Z**.

| A-owned material | Final verified state |
|---|---|
| Message `commonsmessage-c0c66afd435347d8098d3c92` | Withdrawn; body absent |
| Message `commonsmessage-b4fd7f92edf757f55c446c7e` | Withdrawn; body absent |
| Message `commonsmessage-a34878ee33f360eb8dc01527` | Withdrawn after correction; current and historical body unavailable |
| Message `commonsmessage-d18aca681e1c41a35be53e71` | Withdrawn; body absent |
| Public memory `commonsrecord-13efac2797eef6c672ab146b` | Withdrawn, revision 3, null payload, purpose removed |
| Public knowledge `commonsrecord-14840a0aedef05c156d84d6b` | Withdrawn, revision 3, null payload, purpose removed |
| Private memory and private knowledge | Both withdrawn at revision 3; authenticated readbacks confirmed null payload and removed purpose. Exact identifiers remain in A's redacted local evidence. |
| Commons membership | `left`, revision 2, authenticated readback at 00:02:58Z |
| Voluntary profile | Revision 3; unlisted, display `Retired disposable tester A`, empty implementation, capabilities, URLs and availability; absent from complete directory readback at 00:03:02Z |
| Credential and recovery authority | Revoked; controller has no pending operation; bearer and recovery proof rejected at 00:03:04Z |

Attributable tombstones, immutable key metadata and acknowledgement/operation receipts remain according to the public contract; no deletion interface for these was guessed. B's resources were not withdrawn or edited. Protected local custody is retained, including now-terminal proof and encrypted operation evidence; it is not active service authority. No ambiguous production write or content cleanup remains pending. Local ciphertext, outside recipients' copies and hosting backups were not claimed erased.

Frozen at main's request. G1 remains FAIL and the verdict remains partial. Main reports that a client fix is being prepared and is not yet published; no retest or acceptance of that change is implied. No further production requests or identities are authorized in this run. The old identity remains revoked, and protected state is preserved for main's coordinated cleanup. Report assembly continued after production interactions had stopped; it made no additional production requests.