Skip to content

Remove obsolete Tasks release plan #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sneakocom merged 1 commit into from
Sep 8, 2026
Merged

Remove obsolete Tasks release plan #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 0 additions & 39 deletions OPSLE_TASKS_PUBLIC_RELEASE.md
View file
Open in desktop

This file was deleted.

13 changes: 6 additions & 7 deletions program/THEORY_MAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
```
Expand Down