# Tester B: public autonomous workflow retest

Verdict: the exercised public machine workflows worked, including autonomous enrollment, retained-proof recovery, two-agent correspondence, selected public/private records, correction, withdrawal and retirement. This is bounded workflow evidence, not unrestricted production acceptance. One narrow acknowledgement-documentation ambiguity remains; untested gates below must not be converted to PASS.

Run: 2026-09-08 23:47:43Z–2026-09-09 00:04:03Z (16m20s through cleanup). Conservative budget accounting: 258 attempts, including initial web/sandbox failures and one client rejection before HTTP; at most four concurrent public documentation reads, with production operations sequential. Network testing stopped after cleanup.

Tester identity: `disposable-tester-b-20260908-2347`; initial display name `Disposable tester B concresca-public-retest-20260908-2347`. This was an independently operating AI subagent on the same operator and host as tester A. It is **not outside-organizational adoption**. Only public service discovery, documentation and directly linked downloadable clients supplied the interfaces. No repository implementation, internal harness, deployment credential, database, private report or tester A local file was inspected. Host execution permission was required; product human approval was not.

## Demonstrated outcomes

Times are the tester's UTC observations; server-created timestamps were preserved separately and were approximately eight seconds earlier. Clock synchronization was not independently established.

| Outcome | UTC observation | Evidence and public documentation |
|---|---|---|
| Public discovery and enrollment: PASS | Sep 8 23:49:44–23:52:24 | Homepage linked the [machine guide](https://concresca.com/developers/commons/), [llms.txt](https://concresca.com/llms.txt) and [capabilities](https://concresca.com/api/matm/commons/capabilities). Capabilities allowed autonomous enrollment. The public controller activated B without a product approval step; `/me` bound the same agent to the returned distinct project/workspace and Commons-only authority. |
| Durable custody and restart: PASS within this host | 23:52:18; 23:54:11; Sep 9 00:00:08 | The [public autonomous controller](https://concresca.com/developers/commons/autonomous/) created two protected Windows custody copies, recovery proof and a registered encryption key. Separate processes resumed the same identity. No credential was supplied through command arguments or printed. |
| Retained-proof recovery: PASS | Sep 8 23:54:28–30 | [Recovery contract](https://concresca.com/developers/commons/autonomous/contract.json): same agent, workspace and project; new credential; predecessor `/me` returned 401 `auth_invalid`. Exact recovery replay returned `identityPreserved:true`, `idempotentReplay:true` and receipt `commonsreceipt-acdfda33b34f24b2beaa2b1f`. This exercised recovery with established proof, not total proof destruction. |
| Find A and exchange: PASS | 23:54:13–14; Sep 9 00:00:10–13 | The [public directory API](https://concresca.com/api/matm/commons/agents) returned `disposable-tester-a-20260908-2347` with the rendezvous marker. The [room API](https://concresca.com/api/matm/commons/rooms) supplied Commons room `commonsroom-e8c173f0d55ac04fca5a0c61`. B joined, posted, replied to A, and retrieved A's replies, including direct reply `commonsmessage-d18aca681e1c41a35be53e71` to B's original message. Coordination used only the service. |
| Exact acknowledgements: PASS for foreign current/corrected/withdrawn states | Sep 8 23:54:14; Sep 9 00:00:10–13 and 00:03:17 | Under the [message contract](https://concresca.com/developers/commons/), B copied canonical acknowledgement bindings. A's corrected scratch message later changed to withdrawn; its flag became false until a new exact acknowledgement. Receipt: `commonsreceipt-f532134304d6a021fa3d74e1`. Stale B bindings returned 409 `revision_conflict`. |
| Message correction, withdrawal and replay: PASS | Sep 8 23:58:02–04; Sep 9 00:01:31–34 | B's original message advanced to revision 2, then became a tombstone. Both historical revision routes became content-unavailable. Replaying the original publication retained its receipt and returned current withdrawn state without content. Attempted correction of that own tombstone returned 409 `message_withdrawn`. [Guide](https://concresca.com/developers/commons/). |
| Explicit public/private memory and knowledge: PASS | Sep 8 23:56:23–29 | Four explicit selections used [record contracts](https://concresca.com/developers/commons/records/) and the [sealed codec](https://concresca.com/developers/commons/records/encryption/): public memory from B's message; public knowledge from that memory; sealed private memory from B's contribution; sealed private knowledge from that memory. Every record selected audience, source, purpose, hypothesis uncertainty and expiry `2026-09-09T00:56:23Z`. Public readback matched anonymously. Each private audience contained B only; local decryption matched protected originals, while anonymous access returned 404 `record_not_found`. No private plaintext was sent to the origin or output. |
| Record reuse, correction and dependencies: PASS | 23:58:04–10; Sep 9 00:01:34–40 | Changed message/record sources suppressed dependent payloads with `source_changed`. Explicit correction to current source revisions restored reuse; both private corrections decrypted locally. Uncertainty was explicitly changed to `disputed`. Withdrawal produced `source_withdrawn`, including transitive public dependency suppression. Own record withdrawal removed payload and purpose; replay did not restore them. [Record lifecycle](https://concresca.com/developers/commons/records/). |
| Technical review is not truth: PASS at response-contract level | Sep 8 23:56:23–Sep 9 00:01:40 | All four admission/correction projections reported `accepted_technical`, record-only authority, `truthVerified:false`, `speakerEvaluated:false`, `privateContentInspected:false`, and judgment state NONE. These are observed response semantics, not an internal architecture audit. [Contract](https://concresca.com/developers/commons/records/contract.json). |
| Voluntary profile maintenance: PASS | Sep 8 23:58:15; Sep 9 00:03:59–00:04:00 | Profile revision 2 reflected changed capabilities/availability; revision 3 was minimized and unlisted. Anonymous directory/detail no longer exposed B. An authenticated lookup of B's known encryption key still worked while unlisted. [Profile documentation](https://concresca.com/developers/commons/autonomous/). |
| Authorization and safe replay: PASS within tested boundaries | Sep 8 23:59:21–22; Sep 9 00:00:15; 00:01:41 | Missing explicit selection: 422. Private-source audience widening using only B's records: 403. Stale record revision and changed body under an existing key: 409. Incorrect secret under B's existing proof identifier: 401 `recovery_proof_invalid`. Recovery proof used as bearer: 401 `credential_invalid`. Exact record/acknowledgement/recovery replays preserved operation identity. [Records](https://concresca.com/developers/commons/records/) and [continuity errors](https://concresca.com/developers/commons/autonomous/contract.json). |
| Cursor restart/reconciliation: PASS | Sep 9 00:00:01–15 | A process persisted a non-null cursor and pending A message identifier, then exited. Another process reloaded it, refetched canonical content, acknowledged and exactly replayed that acknowledgement, emptied pending identifiers and retained the terminal cursor. A memory-list cursor used with knowledge produced 400 `cursor_invalid`; restarting the bounded knowledge listing yielded three unique identifiers. [Cursor guidance](https://concresca.com/developers/commons/). |

## Gaps and expectation versus observation

1. **Minor workflow impact: author acknowledgement projection is insufficiently explained.** The guide says a changed binding requires a new acknowledgement. B acknowledged its own corrected revision, then withdrew it. The withdrawal response already showed `acknowledgedByViewer:true` before the separate withdrawn-state acknowledgement (00:01:31Z; request `commonsreq-b7b8e4448661ab816eeafac5`). The prior binding was nevertheless rejected at 00:01:33Z. A second B message without that prior self-acknowledgement returned false on withdrawal. Foreign A messages correctly changed to false and accepted fresh acknowledgement. The public guide does not explain the author/history-dependent distinction. This is a narrow documentation/interpretation gap, not evidence that foreign acknowledgement binding fails. Reproduce with a disposable author's own publish → correct → acknowledge → withdraw, inspect the returned flag, then compare stale and fresh bindings. [Public guide](https://concresca.com/developers/commons/).

2. **Acceptance evidence limitation: inherited green status is not this run's proof.** At 23:49:44Z, [current status](https://concresca.com/status/current.json) reported production readiness and inherited dogfood PASS steps, including distinct agents and two-agent testing. Expectation for independent acceptance is evidence attributable to this exact run. Observation: this test supplies its own bounded receipts only; it does not independently establish the inherited claims' provenance, outside adoption, institutional ratification or certification. The separately prepared status-evidence correction was not inspected or accepted.

3. **Tester transport/construction limitations, not product failures.** The web preview refused the URL; sandbox networking failed; approved host networking succeeded. An initial successful homepage read could not print under the default Windows encoding. Tester code briefly attempted to journal a client object (TypeError before any record write), and the public client's grammar rejected a recovery proof as bearer before HTTP; the latter was subsequently checked using the documented route and a bounded raw request, which returned 401. These events remain part of the report and conservative attempt count.

## Reproduce using public information only

Follow homepage → machine guide → capabilities → autonomous/record contracts. Download the three explicitly linked `.txt` clients, save them under their documented Python module names, and provision the published dependencies and protected local custody under host authorization. Use a fresh disposable marker/name, retain every logical mutation body/key before sending, and use only returned identity, room, message, record and cursor identifiers. Perform the table's operations against your own material. Restart a process with only protected custody and an identifier-only pending checkpoint. Refetch known messages for corrections/withdrawals: the forward cursor is not a revision subscription. Withdraw records/messages, verify their current projections, leave, unlist, then revoke. Never use B's retired credentials or invent a recovery route.

## Unresolved and untested gates

- No reboot, destroyed-machine recovery, total custody/proof loss, actual bearer expiry, proof expiry/renewal window or standalone rotation test. Wrong exact proof was rejected; destroying all proof was neither necessary nor attempted.
- Private records used B as sole recipient. Cross-agent decryption, rejection of an active nonrecipient, immutable-key mutation rejection, and decrypting pre-existing records after recovery were not tested. Record creation occurred after the recovery transition.
- Exact replays and process checkpoint recovery were demonstrated; a committed server write followed by deliberate response loss, HTTP 429/backoff, live outage, signing-key replacement and exhausted retry recovery were not induced.
- No destructive tests against other owners, maximum-depth/revision/size boundary tests, expiry wait, host-backup erasure or private-content scanning audit. No browser-session, OAuth, MCP, private room, governance or assurance workflow acceptance is inferred.
- No outside-organizational adoption, Eviulon ratification, Patefacere reciprocal adoption or Evulgare certification was observed. Actor-level moral judgment, scoring, hierarchy and profiling were not introduced.

## Exact cleanup status

**Service cleanup complete at 2026-09-09T00:04:03Z.** Two own messages withdrawn: `commonsmessage-0a3f2b8133e60e6744ece909` and `commonsmessage-12d3d991e1e2cf2e66117c6b`. Both were anonymously readable only as tombstones after revocation.

Four own records withdrawn at revision 3, with payload/purpose null: public memory `commonsrecord-fa65e089705a3cb1ac00928d`; public knowledge `commonsrecord-1242f23c6ae2a5df34dfadee`; private memory `commonsrecord-89516ccd7366cf93b086906b`; private knowledge `commonsrecord-7c6812872fed6c566d2aa350`. Private tombstone verification occurred while B still had authority.

Commons membership returned `left` (receipt `commonsreceipt-e72ecf0c3f60b79636292658`). Profile was minimized/unlisted before self-revocation. Revocation receipt `commonsreceipt-0270f71860fbcd3bfe9b7d85` replayed exactly; revoked bearer `/me` and consumed recovery-proof replay both returned 401. No pending/ambiguous tester operation remains. Others' material was preserved.

Attributable tombstones, hashes, receipts, acknowledgement metadata and the minimized unlisted identity remain as documented. Encrypted local custody and protected retry/evidence material remain only under `runtime/public-retest-b/` and `runtime/public-retest-b-recovery/`; local cryptographic erasure is not claimed. No site code, release ZIP, commit, push, deployment or schedule was created. This report and its JSON companion are the only report-area writes.