1f07737bf5
Per CEO approval 2026-10-04. Option (a): overwrite v1 with v2. Changes: * send-mailbox-message.sh - production implementation with zero placeholders. Real rail callbacks via urllib.request POST to submit_request. EXECUTOR_API_KEY in Authorization header only. * delivery-pack.sh - informational template (main script generates per-recipient copies inline). * SKILL.md - v2 spec (what's new + what's the same). * v2-vs-v1-diff.md - side-by-side diff. * README.md - bundle index. Honours brief locked decisions [1]: - Decision 2: outbox canonical; inbox mirrored (own inbox only). - Decision 6: mailbox writes AUTO_RUN per recipient. - Decision 7: append-only inheritance; this skill is additive. - Decision 8: naming convention coreci-<role> validated at parse. - Decision 9: extend, don't duplicate. Does NOT (per brief): - Edit coreci/agent-definitions/ (read-only per Rule #7). - Implement deny_read_targets (xfail; out of scope). - Classify mailbox writes as NEEDS_APPROVAL. - Write to anyone else's outbox/. - Provide cross-repo atomicity (per-recipient only).
1.3 KiB
1.3 KiB
send-mailbox-message v2 — production-ready
Files
SKILL.md— human + LLM contract (v2 spec)send-mailbox-message.sh— production shell implementation (zero placeholders; real rail callbacks)delivery-pack.sh— informational template (use the main script to generate per-recipient copies)v2-vs-v1-diff.md— what changed between v1 and v2README.md— this file
Status
v2 is the version intended to land at
coreci/executor-config/tools/mailbox/send-mailbox-message.sh.
v1 (the reference impl with placeholders) is kept for reviewer
audit and educational purposes.
Dependencies
- Brief D1–D6 must be in place (D1, D2, D3, D4, D5, D6). [1]
- v4.1 mailbox-path exemption must be in place (currently parked;
0d6f5d32220bawaiting CEO click). [1] ~/.mailboxrcper sender (machine-readable schema).- Org-wide
coreci/executor-config/mailbox-gates.yamlfor compliance gate config (one source of truth for the org).
How to test locally
The script depends on the executor's standard credential envelope, so it must be invoked via the rail as a bash_pack. There is no local-runnable test harness — the rail is the only sanctioned write path [1]. The test matrix T18–T30 documents expected behaviour for reviewer audit.
What this skill does NOT do
See SKILL.md "What this skill does NOT do" section.