A Codex-default session runtime and unified workbench for research, grant, and presentation work
Start work through Codex-default sessions, activate domain agents when needed, and let optional shells share the same runtime truth
|
Who It Serves Clinicians, researchers, PIs, educators, and small teams who want one entry point for long-running expert work |
What It Helps Manage Conversations, workspace-based tasks, progress updates, delivered files, and specialized workflows |
Current ScopeOPL is the top-level workbench for the product family, with active coverage in medical research, grant work, and presentation delivery
|
OPLgives one place to start work, keep progress legible, and collect outputs, while each specialized product family keeps its own methods and deliverables.
- Start a general conversation or a multi-step task from the same workbench.
- Open workspace-based work when a task needs a fixed directory and file context.
- Run specialized product families for research, grant, and presentation work.
- Keep long-running progress visible in plain language.
- Gather manuscripts, proposals, slide decks, tables, review files, and other deliverables in one place.
| Product family | Current product | Best for | Typical deliverables |
|---|---|---|---|
Research Foundry |
Med Auto Science |
Medical research, evidence organization, manuscript preparation | Analysis packages, evidence packages, manuscripts |
Grant Foundry |
Med Auto Grant |
Grant direction setting, proposal writing, revision work | Proposals, outlines, revision packs |
Presentation Foundry |
RedCube AI |
Lectures, lab talks, reports, defense materials | Slide decks, scripts, presentation packages |
Thesis Foundry |
Planned | Thesis assembly and defense preparation | Chapter drafts, defense materials |
Review Foundry |
Planned | Review, rebuttal, and revision work | Review comments, response drafts, revision plans |
- General work for discussion, planning, reading, and common tasks.
- Workspace-based work for tasks that need a real directory and persistent file context.
- Specialized product families for domain-specific expert workflows.
- Progress and file views that stay attached to ongoing work.
- Central management for engines, modules, and health status.
- The Codex-default session/runtime path and public projection surfaces behind the product family.
- The activation and dispatch layer that maps
OPLand domain-agent invocations onto repo-owned capability surfaces. - Engine and module management.
- Workspace, session, progress, and artifact discovery surfaces.
- Machine-readable contracts for the shared product layer.
The full GUI shell is maintained in an external overlay repository.
This repository tracks the Codex-default runtime contract, the OPL activation layer, and the shared truth consumed by local opl, GUI shells, and compatibility surfaces.
- Potential users and human experts should start here, then continue to Roadmap, Task Map, and Operating Model.
- Technical readers and planners should continue to Docs Guide, then read Project, Status, Architecture, Invariants, and Decisions.
- Developers and maintainers should use Contracts Overview, Reference Index, and the tracked records under
docs/specs/,docs/plans/, and History Archive.
If you are handing OPL to Codex or another general-purpose Agent, start here
- Read the Docs Guide first. It already consolidates the current product model, technical working set, contract entry points, and document layering.
- Then read Project, Status, Architecture, Invariants, and Decisions. This is the fastest way to recover the top-level boundary, the Codex-default runtime contract, the explicit activation layer, and the admitted domains.
- The default frontdoors are
opl,opl exec, andopl resume. They inherit Codex-default semantics unless you explicitly switch runtime or activate a domain agent.MCPstays the supported protocol layer, andcontrollerstays internal. - The active interaction route is Codex-default first: local
opl, directCodexusage, and future external shells all consume the same session/runtime truth. Runopl skill syncwhen you want the family domain skill packs available inside Codex; explicit runtime switches stay opt-in. - The current active domain agents are
Med Auto Science,Med Auto Grant, andRedCube AI. They expose stable capability surfaces as local CLIs, programs/scripts, and repo-tracked contracts; continue into Status, Architecture, and the OPL Public Surface Index to recover the family mapping and public entry surfaces. - Use
OPLwhen the task needs the top-level session/runtime path, sharedworkspaces / sessions / progress / artifactssurfaces, or explicit domain activation. Use the corresponding domain repository when the task is already scoped to one domain and you want that repo's own CLI/scripts/contracts boundary.