Man1Lab v1.3.0
Execution Runtime · Materialization · Durable Local Runs
Release date: 2026-07-14
What's New
Execution Runtime
Man1Lab can now run a materialized reproduction plan on a durable local execution platform.
The Runtime layer now manages:
- Execution Engine lifecycle and sequential scheduling
- Runtime-owned
ExecutionStorewith atomic snapshots - Append-only traces, artifact manifests, and reports
- Cross-process interruption, reload, and conservative reconciliation
- Resume of reusable successful tasks after artifact validation
Planning-to-Execution Materialization
Abstract Planning graphs are converted into immutable local task specifications before an ExecutionRun is created.
ExecutionStrategy + ExecutionGraph
│
▼
Execution Materialization
│
▼
READY gate
│
▼
LocalExecutor run + durable report
Incomplete, conflicting, or unsupported cases are rejected safely as BLOCKED, UNSUPPORTED, or RECONCILIATION_REQUIRED — before execution begins.
Execution Evidence & Preparation
Discovery can now supply typed, pinned execution evidence for bounded reproduction workflows.
Supported evidence types include:
- Repository (workspace or pinned Git)
- Dataset and checkpoint sources
- Configuration (existing file or deterministic render)
Bounded preparation operations produce manifests, checksums, safe extraction, and receipts for inspectable runs.
One-Command Reproduction Path
When Discovery evidence is complete and conflict-free, Man1Lab can orchestrate the full path in one application flow:
Analysis → Discovery → Planning → Materialization → Execution → Report
Facade and console execution commands are integrated with LocalExecutor for local subprocess runs with durable logs and artifacts.
Improvements
- Stronger readiness gate between Planning and Execution
- More inspectable preparation and workload artifacts
- Better crash recovery for completed tasks
- Safer handling of missing or unsupported evidence
- Provider-driven DeiT release acceptance covering pinned evidence and real process interruption
- Expanded regression and release acceptance testing
Compatibility
No breaking changes to existing Planning, Runtime, Facade, or console boundaries.
CLI commands, SDK APIs, configuration files, and canonical planning artifacts remain compatible with previous releases.
Reproduction executes only when Discovery supplies complete, conflict-free, pinned execution evidence. This release does not claim arbitrary-paper reproduction. Authenticated downloads, Docker, remote GPU, cluster, and robot backends remain out of scope.
Current Workflow
Paper
│
▼
Analysis
│
▼
Research Resource Discovery
│
▼
Execution Planning
│
▼
Materialization
│
▼
Local Execution
│
▼
Report
Execution is available for bounded, evidence-backed local runs. Broader backend support remains under active development.
Statistics
- 997 tests collected
- Execution Engine
- Runtime ExecutionStore
- Planning-to-Execution Materialization
- Typed Execution Evidence
- LocalExecutor Platform Integration
- One-Command Orchestration
- DeiT Release Acceptance
Thank you for using Man1Lab.