docs: record send sent diagnostic intake

This commit is contained in:
zhaoyilun
2026-07-11 00:25:54 +08:00
parent c8b619c254
commit 6164703a9a
5 changed files with 440 additions and 2 deletions

View File

@@ -0,0 +1,55 @@
# Returned send-sent record diagnostic intake - 2026-07-10
## Inputs reviewed
- `send-sent-record-diagnostic-package1(1).zip`
- `send-sent-record-diagnostic-package2(1).zip`
The raw packages stay outside the repository. This note records only safe summary fields.
## Validator
Added `scripts/validate-send-sent-record-diagnostic-package.ps1` for this package family. It outputs booleans and counts only; it does not print raw target id, raw message body, raw idempotency key, or local operator paths.
## Safe validation summaries
Package 1:
```json
{"ok":true,"package_type":"send-sent-record-diagnostic","package_file_name":"send-sent-record-diagnostic-package1(1).zip","summary_json_present":false,"input_json_present":true,"content_sha256_matches_input":true,"before_run_count":1,"after_run_count":1,"exact_content_seen_after":false,"content_sha256_seen_after":false,"after_offline_blocked":true,"operator_observed_success":true,"do_not_send_second_time_confirmed":true,"production_send_enabled":false,"automatic_send_enabled":false,"strict_send_record_pass":false,"production_send_unlock_recommended":false,"decision":"manual_success_without_machine_sent_record"}
```
Package 2:
```json
{"ok":true,"package_type":"send-sent-record-diagnostic","package_file_name":"send-sent-record-diagnostic-package2(1).zip","summary_json_present":true,"input_json_present":true,"content_sha256_matches_input":true,"before_run_count":1,"after_run_count":1,"exact_content_seen_after":false,"content_sha256_seen_after":false,"after_offline_blocked":true,"latest_after_route_hints":["A_ROUTE_INCOMPLETE","A_ROUTE_OFFLINE_BLOCKED"],"operator_observed_success":true,"do_not_send_second_time_confirmed":true,"production_send_enabled":false,"automatic_send_enabled":false,"strict_send_record_pass":false,"production_send_unlock_recommended":false,"decision":"manual_success_without_machine_sent_record"}
```
Strict mode was also checked against package 2 and failed, as expected, because `strict_send_record_pass=false`.
## Business interpretation
The two packages improve confidence that a human operator successfully sent the fixed sandbox message once. They do not prove that the bridge can safely enable production send, because the machine-verifiable sent-record evidence is still missing:
- `exact_content_seen_after=false`
- `content_sha256_seen_after=false`
- `after_offline_blocked=true`
- package 2 after route hints include `A_ROUTE_INCOMPLETE` and `A_ROUTE_OFFLINE_BLOCKED`
## Decision
Production `isphere_send_message` remains blocked. Current usable state remains:
- send-message preview/dry-run: usable
- audit and idempotency: usable
- production send: blocked by missing strict machine sent-record evidence
## Next requirement for unlocking production send
A future online package must show all of the following without printing raw body/target/path values:
1. before and after recorder outputs are present;
2. content hash or sent-record marker is visible after send;
3. offline blocker is absent after send;
4. operator confirms only one send was performed;
5. strict validator returns `strict_send_record_pass=true` and `production_send_unlock_recommended=true`.