diff --git a/OPSLE_TASKS_PUBLIC_RELEASE.md b/OPSLE_TASKS_PUBLIC_RELEASE.md
deleted file mode 100644
index 1d26fd1..0000000
--- a/OPSLE_TASKS_PUBLIC_RELEASE.md
+++ /dev/null
@@ -1,39 +0,0 @@
-# Future Opsle Tasks public release
-
-> Planning only. Taslos Tasks remains private in its existing location. Publication was not executed.
-
-This release is LATER program work. It does not begin merely because Opsle Tasks
-becomes the NEXT Durable Supervisor workload; it requires separate explicit
-release authority and the eligibility evidence below.
-
-## Full-history audit
-
-Audit every reachable commit, tag, branch, release asset, PR artifact, LFS object, submodule reference, and archive for credentials, tokens, private keys, connection strings, private addresses, environment secrets, database data, backups, logs, sensitive screenshots, and accidental artifacts. Removing a value from HEAD is insufficient if reachable history retains it.
-
-## Security
-
-Review authentication, authorization, external operator API, worker authority, broker, credential transport, arbitrary execution, path traversal, shell/SQL injection, SSRF, filesystem exposure, debug endpoints, deployment authority, redaction, and unsafe defaults.
-
-Server-side identity/current grants are authoritative. Never trust client-provided user, role, project, permission, approval, worker, lease, fence, or source identity. UI hiding is secondary.
-
-## Self-hostability
-
-Users should be able to clone, configure, install, connect providers, create project/objective/task, execute isolated work, verify, review, observe, back up, restore, and upgrade without private infrastructure.
-
-## Documentation
-
-Require README, architecture, threat model, installation, configuration, providers, development, deployment, backup, restore, upgrade, troubleshooting, contribution, security, license, release/versioning.
-
-## Eligibility
-
-- development/readiness gate = PASS;
-- production release verified;
-- exact repository/deployment parity;
-- required tests pass;
-- security audit passes;
-- full-history secret audit passes;
-- self-host docs sufficient;
-- license complete;
-- no known publication blocker.
-
-Visibility changes only in the separately authorized release project. It did not change during this bootstrap.
diff --git a/program/THEORY_MAP.md b/program/THEORY_MAP.md
index 5c0016e..eb393ab 100644
--- a/program/THEORY_MAP.md
+++ b/program/THEORY_MAP.md
@@ -450,26 +450,25 @@ authorized by the provider-free preparation. Controlled experiments are now
 LATER program work rather than the immediate execution; the authoritative
 current priority is the machine state in `program/registry.json`.
 
-## Public Opsle and Taslos Tasks boundary
+## Public Opsle and predecessor boundary
 
 The 2026-08-25 extraction snapshot is historical provenance, not a dependency
-direction. Taslos Tasks remains private/active and unchanged. Production
-complexity demonstrated that several mechanisms were possible, but does not
-establish their general primitives, repository boundaries, or comparative
-benefit.
+direction. The retired predecessor demonstrated that several mechanisms were
+possible, but does not establish their general primitives, repository
+boundaries, or comparative benefit.
 
 The long-term direction is:
 
 ```text
 public Opsle mechanisms and protocols
                 ↓
-future public Opsle Tasks and other products consume pinned versions/adapters
+Opsle Tasks and other products consume pinned versions/adapters
 ```
 
 It is not:
 
 ```text
-private Taslos Tasks remains the canonical implementation
+the retired predecessor remains the canonical implementation
                 ↓
 public concepts are repeatedly rediscovered after production coupling
 ```