Interim Operating Environment

The Guide Is Becoming the Workbench Portal.

Until a stable core runtime is selected, the Guide is the front door to the small working apps already built for modeling, tensions, library work, and other capability experiments.

Portal Mode Runtime TBD Small Apps First

The Guide Is the Stable Front Door.


The Guide no longer depends on OpenClaw as the core operating environment. That path was abandoned because the maintenance burden was too high for the role it needed to play.

In the interim, the Guide becomes a lightweight portal: a coherent place to find, explain, and launch the small apps that already demonstrate pieces of the Workbench. The operating layer can change later without hiding the work that is already usable now.

Current Operating Model


The next durable runtime has not been selected. Rather than tying the Workbench to another operating environment too early, the Guide can serve as the stable surface above the experiments.

Each small app remains independently deployable and maintainable. The Guide gives users one place to understand what each tool is for, when to use it, and where to go next.

Now
Guide portal → small apps → focused method experiences
The portal makes the collection legible while avoiding a high-maintenance orchestration layer.
Later
Stable runtime → shared state, identity, handoffs, and guided sequencing
The future operating environment should earn its place by reducing maintenance and preserving the apps already working.

App Portal


These are the current tools the Guide should make accessible first. The portal role is not to merge them prematurely; it is to help users choose the right entry point.

What the Guide Does Now


For now, the Guide is less runtime and more wayfinding layer. It gives the Workbench a coherent front door while the underlying operating environment remains open.

In Scope

  • Explaining what each small app is for
  • Routing users to the right tool for their current task
  • Maintaining a clear inventory of live, local, and experimental apps
  • Framing tools through TUG methods and the Workbench architecture
  • Preserving a stable product surface while the runtime decision is deferred

Out of Scope

  • Maintaining OpenClaw or any abandoned orchestration layer
  • Forcing all tools into one shared state model before the runtime is selected
  • Promising automated skill invocation before the operating layer exists
  • Payments, billing, and enterprise account management

Stakeholders

  • Users trying to choose the right Workbench tool
  • Builders maintaining focused capability apps
  • Product decision-makers evaluating the next operating environment
  • Partners who need to see what is already working

Success

Users can find a working tool quickly, understand why that tool matters, and move from one capability to another without needing to understand the underlying technical experiments.

PASS Methodology


The Guide navigates users through TUG's four-phase process.

Program
Clarify strategy, align stakeholders, and define success criteria.
Analysis
Map the as-is environment through systematic observation: observe, model, align.
Synthesis
Iteratively develop and test new concepts, then design the to-be state.
Sustain
Operationalize solutions, build governance, and plan for ongoing evolution.

Core Tensions


Helpful vs. Agency-Preserving
Illuminate options while letting users make decisions.
Thorough vs. Efficient
Balance depth with user time constraints.
Instrument vs. Scaffold
The Agency Dial determines how much the Guide does for the user versus with the user.

Runtime Selection Criteria


The next operating environment should be selected by what it lets the Workbench stop worrying about. It should make the small apps easier to run together, not harder to maintain individually.

Low Maintenance
The runtime should reduce operational load, not create another system that needs constant care.
App Preservation
Existing tools should keep working as independent apps while gaining better navigation and handoff.
Shared Identity
When needed, users should carry project context across tools without every app owning account logic.
Clear Handoffs
Outputs from one tool should become inputs to another without requiring brittle orchestration.
Replaceable Core
The product surface should survive a runtime change. The Guide portal is the continuity layer.