Workbench · Workflows & capabilities / Code & architecture

Skeleton

Explore a local workbench for publishing capability versions and recording permitted or refused execution.

Explore the repository ↗Try or inspect it ↓

Actual local execution with synthetic input. Later TypeScript workbench with real local Python execution. It is separate from the historical Python node-graph generation.

A function becomes a version you can run.

An unpublished action is refused. Editing the draft leaves v1 unchanged; publishing v2 changes the output, and rollback creates v3 with the earlier behavior. The original v1 record remains unchanged.

Example input

{"value":"  hello   world  "}

Captured result

{
  "example": "Text Normalizer: draft to recorded execution",
  "input": {
    "value": "  hello   world  "
  },
  "unpublished_request": {
    "http_status": 403,
    "status": "denied",
    "reasons": [
      "Package has no published release.",
      "Published release record is missing.",
      "Published release validation is not passing."
    ]
  },
  "validation": true,
  "published_version": 1,
  "execution": {
    "status": "complete",
    "output": "hello world"
  },
  "external_model_calls": 0,
  "scope": "Actual local runtime and Python execution with synthetic text. This is not a security sandbox."
}

Try the example.

Node.js 20+ and Python 3.10+. Run from a fresh checkout; no model account is needed.

npm ci --ignore-scripts
npm run build
npm run demo

An unpublished action is refused. Editing the draft leaves v1 unchanged; publishing v2 changes the output, and rollback creates v3 with the earlier behavior. The original v1 record remains unchanged.

Complete setup and instructions ↗

The interesting part.

The integrated workbench makes package lifecycle, agent policy and execution evidence visible together.

Integrated source snapshot

Where it came from.

Later owner-governed TypeScript composition host from the broader local workbench.

Publishes the complete newer rebuild, owner contracts and migration evidence; excludes the legacy application.

Neither the historical Python node-graph workbench nor a file-for-file port; current code must not be described as embedding this Rubric Rumble release.

Source ↗

Follow the family: Skeleton and the ownership rebuild

Focused extractionCapability Package Workbench
Inspect or reuse this boundary without navigating the whole application. The parent implementation remains present. The relationship is provenance, not a package-manager dependency.
Source ↗
Focused extractionAgent Workflow Governance
Inspect or reuse this boundary without navigating the whole application. The parent implementation remains present. The relationship is provenance, not a package-manager dependency.
Source ↗
Focused extractionBounded Execution Ledger
Inspect or reuse this boundary without navigating the whole application. The parent implementation remains present. The relationship is provenance, not a package-manager dependency.
Source ↗
Earlier design generationPython Agent Foundry Workbench
Compare the earlier integrated implementation with the later ownership-governed architecture. Carries questions forward; not a file-for-file port and not a statement about every historical Skeleton generation.
Source 1 ↗, Source 2 ↗
Architecture methodThe Seven Ownership Architecture
Inspect the architecture and its worked review method independently.
Source ↗