Skip to content

Document controlled-session integrations #54

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
omry merged 1 commit into from
Aug 14, 2026
Merged

Document controlled-session integrations #54

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
2 changes: 2 additions & 0 deletions .changes/unreleased/controlled-session-user-guide.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
kind: Docs
body: Document controlled-session setup, controller integration, lifecycle and failure handling, security boundaries, and focused OmegaFlow, agent, and inspection profiles.
11 changes: 10 additions & 1 deletion docs/CONTROLLED_SESSION_DESIGN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1894,7 +1894,7 @@ while the public host command still reports the session failure. The fixture
adds no OmegaFlow code, private-protocol dependency, runtime dependency
installer, or public Reploy surface.

### Slice 6: User-Facing Documentation
### Slice 6: User-Facing Documentation (implemented)

After the generic runtime and at least one integration profile are proven,
publish user-facing documentation before public release. Explain the
Expand All @@ -1904,6 +1904,15 @@ contracts, and the security defaults and limitations. Include focused examples
for OmegaFlow recording, sandboxed agents, and security inspection without
presenting any one profile as the controlled-session abstraction itself.

Implementation status: complete. The public controlled-session guide now
covers separate controller and workload staging, exact host invocation,
controller client and attachment use, the strict JSON Lines stream, endpoint
and output grants, lifecycle and failure handling, result and exit semantics,
security defaults, and the initial Linux/Docker limitations. Focused OmegaFlow
recording, sandboxed-agent, and security-inspection profiles demonstrate the
same generic boundary without adding profile-specific Reploy authority. The
site introduction and Capabilities navigation expose the guide.

### Independent Pre-release Runtime Fixes

The admission promotion-versus-cancellation invariant and root-safe
Expand Down
Loading
Loading