# Tester B — fresh post-fix public retest

Verdict: **PASS for the fresh, focused acknowledgement and published-client regression.** Own and independently operated peer messages behaved consistently across current, corrected and withdrawn states. No unexpected production result was observed in the exercised scope. This does not reinterpret, replace or mark the initial B report passed; those reports and the earlier revoked identity were neither accessed nor changed.

Window: 2026-09-09 00:42:39Z–00:51:15Z through verified cleanup, 8m36s. Exactly 166 logged HTTP attempts; maximum two concurrent public-document reads, production operations sequential. One initial PowerShell parsing failure occurred before HTTP and is excluded from that count. No network requests followed cleanup.

New identity: `disposable-tester-b-fix-20260909-0042`, display name `Disposable tester B FIX concresca-public-fix-20260909-0042`. This is a distinct disposable test, not restoration. Tester B independently operated as an AI subagent, with the same operator and host as tester A; outside adoption is false.

## Fresh public sources

- [Machine guide](https://concresca.com/developers/commons/) and [capabilities](https://concresca.com/api/matm/commons/capabilities), fetched 00:43:54Z. Capability availability was true, blockers empty and human approval false. The guide explicitly distinguishes authenticated viewer reads from anonymous projections and says mutations do not implicitly acknowledge a state, including for authors.
- [Autonomous custody guide](https://concresca.com/developers/commons/autonomous/) and [selected-record guide](https://concresca.com/developers/commons/records/), fetched 00:44:13Z.
- [Published coordination client](https://concresca.com/developers/commons/concresca_commons_client.txt), fetched 00:44:19Z, response SHA-256 `071e8a182d593ab7d240b1c418d97cefbb77651bc50e1ee75b95447ed50fef2d`.
- [Published autonomous controller](https://concresca.com/developers/commons/concresca_autonomous_agent.txt), fetched 00:44:20Z, SHA-256 `f6d2c10de94ffd6934b947af372e672d821bd7ef5fd9d5accc7e4699e8775d51`.
- [Published record codec](https://concresca.com/developers/commons/concresca_record_crypto.txt), fetched 00:44:20Z, SHA-256 `70a7ac691b13751ee37705e0f8c450900edb16d4c71ceb151b67d4ddb805a813`; downloaded but private encryption was not exercised in this focused run.

The downloaded clients were not patched. Tester instrumentation counted transport calls and retained protected mutation intent; it did not replace the clients' read authentication or acknowledgement behavior. No repository implementation, internal harness, private report, deployment source or another actor's local files were read. No request targeted the canonical WeaponizedAutonomy identity or site.

## Outcomes and exact evidence

All times below are tester UTC observations. Server timestamps were retained separately and appeared approximately eight to nine seconds earlier; synchronization was not established.

| Outcome | Fresh observation | State |
|---|---|---|
| Autonomous enrollment and custody | Active at 00:46:36Z; public controller established two protected Windows custody copies, recovery proof and a recipient key. Enrollment request `commonsreq-c805d04ee3477065240cb238`. | PASS |
| Published-client viewer readback | 00:46:39Z room and room-list reads returned B's joined membership. At 00:46:42–43Z, message detail and message page returned acknowledged=true after B's exact acknowledgement; a separate anonymous client returned false. At 00:51:06Z authenticated room detail returned membership left. | PASS |
| Find A and exchange publicly | At 00:46:44Z the directory returned `disposable-tester-a-fix-20260909-0042` with the shared marker. B replied to A's root; A's reply `commonsmessage-93335e7f04ef2aa637460700` linked to B's root. Coordination used public room messages only. | PASS |
| Process resume | At 00:47:53Z a separate process resumed the same new B identity and active credential from protected custody. No recovery or restoration of the old B identity occurred. | PASS |
| Own exact acknowledgement lifecycle | B root `commonsmessage-cf06354f5a0e052d5ff8bb9a`: fresh current/corrected/withdrawn reads were false before explicit acknowledgement and true afterward. See receipt table below. | PASS |
| Independent peer lifecycle | B, as viewer, observed A root `commonsmessage-1f11d627fb97da705d59f2bf` through all three states, with false before and true after fresh exact acknowledgement. This establishes B's observations, not private knowledge of A's test execution. | PASS |
| Old replay versus fresh state | For both roots after correction and withdrawal, exact old acknowledgement replay returned the same historical receipt plus the current unacknowledged projection. A subsequent fresh read remained false. Submitting the old binding with a new key returned 409 `revision_conflict`; fresh exact binding then succeeded. | PASS |
| No resurrection | At 00:50:01Z original publication replay returned the current tombstone without content. Both historical revisions returned content unavailable at 00:50:02Z. Attempted correction of B's own tombstone returned 409 `message_withdrawn`. | PASS |
| Optional selected-record regression | Two public records, one memory and one derived knowledge, were created at 00:47:41–42Z with explicit source, audience, hypothesis and one-hour expiry. Source changes suppressed payloads; explicit revision-2 rebinding restored them at 00:48:42–44Z. Source withdrawal suppressed both, including the transitive dependent, at 00:51:01Z. Technical review remained `accepted_technical`, truthVerified=false and speakerEvaluated=false. | PASS, public scope only |
| Invalid configured bearer | After revocation, published-client me, agents, agent, rooms, room, messages, message and revision reads each returned 401 `auth_invalid` at 00:51:12–14Z. Recorded calls retained authentication; no anonymous fallback occurred. Separate anonymous clients could still read the two public tombstones. | PASS |

Fresh acknowledgement receipts:

| Viewer / target state | Before → after UTC | Receipt |
|---|---|---|
| B / own current revision 1 | 00:46:41 → 00:46:42 | `commonsreceipt-0b770428b9e82b1bfa7a0a7d` |
| B / own corrected revision 2 | 00:47:55 → 00:47:57 | `commonsreceipt-572a6ccfb68dc854da8f286b` |
| B / own withdrawn revision 2 | 00:49:59 → 00:50:01 | `commonsreceipt-e621152efec56f274d648ae8` |
| B / A current revision 1 | 00:46:44 → 00:46:45 | `commonsreceipt-e5e56f279851f0e3a50423f0` |
| B / A corrected revision 2 | 00:47:59 → 00:48:01 | `commonsreceipt-c78fc0d801c682590e2cf058` |
| B / A withdrawn revision 2 | 00:50:31 → 00:50:33 | `commonsreceipt-a397f08cff97612cddee8d24` |

## Expectation, gaps and reproducibility

Expected from the fresh guide: mutation does not acknowledge current state; viewer-specific reads use the configured bearer; old receipts do not confer acknowledgement on later states. Observed: those expectations held for B as author and as viewer of independently operated A. No fresh documentation gap or service failure was found in these tested contracts. The earlier report remains a historical observation and is not retroactively changed by this result.

Reproduce from the public guide and downloads: provision authorized protected custody, enroll a fresh disposable identity, discover a peer through its public marker, join the returned room, publish and acknowledge current state. Retain exact bodies/keys. After each author correction or withdrawal, refetch through the configured published client, replay the prior successful acknowledgement, check that current acknowledgement is still false, try the stale binding under a distinct logical key, then submit the fresh canonical binding and read back. Compare an independently constructed anonymous client. Cleanup all own material before revocation, then test configured-client authentication failure and anonymous tombstones separately.

Untested/limited: credential rotation/recovery, proof or bearer expiry, reboot and custody loss; private selected records or cross-agent decryption; cursor interruption recovery, lost committed-response handling, 429/outage/backoff and limit boundaries; browser sessions, private rooms, OAuth/MCP; database/storage/backup or private-content inspection; installed-byte provenance, general readiness, outside adoption or institutional acceptance. The controller established recovery proof, but this run did not use it for recovery. Public record review flags are response observations, not an internal architecture audit. The sole tester construction failure was the initial shell quoting error before any request; approved host transport then worked. No approval or transport blocker remains.

## Cleanup

Complete at **2026-09-09T00:51:15Z**, with no pending writes:

- B root and reply `commonsmessage-3f62c81b62365b620219533c` withdrawn and anonymously read as content-free tombstones after revocation. Withdrawal receipts: `commonsreceipt-fea92edb79f9563f6e4a5118` and `commonsreceipt-8709288b0c850f35b61a688d`.
- Public memory `commonsrecord-2f28e884824e7890ed414fbe` and knowledge `commonsrecord-8dccdcf59040785951712c55` withdrawn at revision 3, payload/purpose null. Receipts: `commonsreceipt-a8bdbfcc2ce30d24fb40ce08` and `commonsreceipt-33c217993355d37635a598d2`. Original memory creation replay also returned withdrawn state without payload.
- Room left, receipt `commonsreceipt-d7df15b287b83d4205e263de`; authenticated detail confirmed left. Profile minimized/unlisted at revision 2 and absent from the public directory before revocation.
- Credential revoked, receipt `commonsreceipt-addd7bb9e32153e984f55e1e`; subsequent configured-client reads all failed authentication.

Documented tombstones, receipts, hashes, acknowledgement metadata and the minimized unlisted identity remain. Encrypted local custody and exact retry material remain under `runtime/public-retest-b-fix/` and `runtime/public-retest-b-fix-recovery/` for main-approved disposal. No local erasure is claimed. Others' resources were preserved. No product/source edits, release, commit, deployment or schedule occurred.