tegwick
9ed8b452a1
issue-core asked us to drop a CoulombCore/port-18765 bridge topology from activity-core-issue-sink. That topology was never in this repo — the only address the playbook carried was a local-dev 127.0.0.1:8765 example. What was actually stale was step 5, which still told workers to coordinate with railiance-platform "when the canonical path ships"; it shipped 2026-07-02 and the lane is active. So: point at issue-core's SCOPE.md for the production address rather than restating it here (ADR-0001), state plainly that no bridge or forwarded port is involved so the next reader does not re-derive the retired topology, and route step 5 through warden route / warden rotate-guide instead of a read. WP-0032-T01 closes as done. What was owed was inputs, not a design, and ZONE-WP-0001-T02 is done carrying all of them — including the two that were corrections to ops-warden's own claims (organization_posture, refused by net-kingdom; and the workload join key, which this repo wrongly said did not exist anywhere). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| playbooks | ||
| AccessManagementDirective.md | ||
| AccessRouting.md | ||
| ActorInventoryPatterns.md | ||
| AuditTrail.md | ||
| CertCommandInterface.md | ||
| CredentialRouting.md | ||
| InterHubBootstrapAccessLane.md | ||
| NetKingdomSecurityMap.md | ||
| OpenBaoSshEngineChecklist.md | ||
| OperatorAccessAssist.md | ||
| OpsWardenConfig.md | ||
| OpsWardenMemory.md | ||
| PolicyGatedSigning.md | ||
| WorkloadSecurityPosture.md | ||