Skip to content

Man1Lab v1.2.0

Choose a tag to compare

@maniac1um maniac1um released this 02 Jul 12:29

Man1Lab v1.2.0 — Platform Capability Release

Release date: 2026-07-03
Codename: Platform Capability
Repository: https://github.com/maniac1um/Man1Lab
Status: Release Candidate


Overview

v1.2.0 completes Platform Capability — the first release where Man1Lab is a unified, installable platform with public interfaces (CLI, Python SDK), integrated Discovery and Execution Planning, and the GitHub Discovery Provider.

v1.1.0 delivered infrastructure foundation. v1.2.0 delivers capabilities and interfaces users interact with directly.

Milestone: Platform Capability
Previous: Foundation Complete (v1.1.0)
Next: Repository Understanding (v1.3)


Highlights

  • Platform FacadeMan1Lab as the single composition root for all interfaces
  • CLIman1lab Typer application (init, doctor, reproduce, analyze, discover, plan, execute, config, version)
  • Python SDKpip install man1lab · from man1lab import Man1Lab
  • Package distribution — PEP 621 pyproject.toml, console script, python -m man1lab
  • Lifecycle commandsman1lab init, man1lab doctor
  • Discovery integratedDiscoveryWorkflowResearchResourceDiscovery (ADR-0013)
  • GitHub Discovery Provider — Collection, Evidence, Verification, Ranking (ADR-0016)
  • Execution Planning integratedExecutionPlanningWorkflowExecutionStrategy (ADR-0014)
  • Strategy-driven PlannerTaskModel from ExecutionStrategy
  • 419 unit tests passing

Architecture Changes

Platform interfaces

CLI  ·  Python SDK  ·  (Future MCP)  ·  (Future REST)
                    ↓
          Man1Lab (Platform Facade)
                    ↓
       TrackedWorkflowOrchestrator
                    ↓
  Reader → Discovery → Execution Planning → Planner
                    ↓
       Coder → Runner → Verification → Review → Report

Canonical artifact pipeline (implemented)

Stage Artifact
Analysis PaperReproductionAnalysis
Discovery ResearchResourceDiscovery
Execution Planning ExecutionStrategy
Planning TaskModel
Implementation Workspace
Execution ExecutionResult
Reporting ReportModel

Future artifacts (planned — not in v1.2.0)

Artifact Milestone
RepositoryKnowledge v1.3 Repository Understanding
Consolidated ReproductionReport Future reporting evolution

ExecutionResult and ReportModel are implemented runtime/report outputs — not renamed to roadmap names above.

Configuration switches

Hydra settings (default enabled):

Switch Effect
discovery.enabled Run Discovery workflow; else empty discovery artifact
execution_planning.enabled Run Execution Planning; else legacy Planner.run_legacy()

CLI Introduction

pip install man1lab
man1lab init
man1lab doctor
man1lab reproduce paper.pdf
man1lab analyze paper.pdf
man1lab discover paper.pdf
man1lab plan paper.pdf
man1lab version

All commands delegate to Man1Lab — no direct orchestrator access.


SDK Introduction

from man1lab import Man1Lab

client = Man1Lab()
client.init()
client.doctor()
report = client.reproduce("paper.pdf")

Public exports: Man1Lab, PLATFORM_VERSION, __version__.


GitHub Discovery Provider

First production external Discovery backend:

Stage Scope
Collection Paper-embedded URLs + conditional search
Evidence Metadata, README, license, activity signals
Verification Exists, accessible, archived, owner match (no clone)
Ranking Deterministic rules — no LLM

Design: github-discovery-provider.md


Package Distribution

Artifact Location
Package metadata pyproject.toml
Console script man1labinterfaces.cli.app:run_cli
Module entry python -m man1lab
Bundled resources conf/, prompts/, .env.example

Breaking Changes

Change Migration
Recommended entry point Use man1lab reproduce or SDK — not python app.py
Planner input (when execution planning enabled) Consumes ExecutionStrategy instead of implicit strategy from analysis alone
Orchestrator pipeline order Discovery and Execution Planning stages run before Planner when enabled

Workflow artifacts remain backward-compatible. PaperReproductionAnalysis unchanged (ADR-0009).

app.py retained for maintainers only — not documented as user entry.


Migration Guide

From v1.1.x (developers)

  1. pip install -e . or pip install man1lab
  2. man1lab init — create workspace and .env
  3. man1lab doctor — validate environment
  4. Replace PYTHONPATH=. python app.py with man1lab reproduce paper.pdf
  5. Optional: set GITHUB_TOKEN in .env for GitHub discovery

From v1.1.x (programmatic)

# Before (maintainer-only)
# PYTHONPATH=. python app.py

# After
from man1lab import Man1Lab
Man1Lab().reproduce("paper.pdf")

Compatibility

Area Status
Pixi development pixi install + pixi run man1lab
pip install pip install man1lab
Legacy app.py Maintainers only
MLflow tracking Optional; TRACKING_BACKEND=noop to disable
Discovery / Execution Planning disable Hydra flags for transitional paths

Known Limitations

Unchanged from prior releases — see CURRENT_STATUS.md:

  • Full training reproduction not guaranteed on benchmark papers
  • Review loop does not re-invoke Coder/Runner on patch
  • RAG blocks delivery defects but not runtime API breakage
  • Shallow Discovery verification does not guarantee runnable repos

Tests

419 unit tests passing (pixi run test).

Platform coverage: facade, CLI, SDK, package distribution, discovery, execution planning, GitHub provider, platform integration.


Related Documents

Document Purpose
CURRENT_STATUS.md Live state
ARCHITECTURE.md Platform architecture
ROADMAP.md Future milestones
v1.1.0 Foundation release
CHANGELOG.md Detailed changelog

Documentation Freeze Audit

Audit performed for v1.2.0 Release Candidate documentation freeze (2026-07-03).

Updated documents

Document Status
README.md ✅ Rewritten — homepage, CLI/SDK primary
docs/GETTING_STARTED.md ✅ Platform workflow
docs/architecture/ARCHITECTURE.md ✅ v1.2 interfaces, artifacts, scope
docs/CURRENT_STATUS.md ✅ v1.2.0, 419 tests, next milestone
docs/releases/v1.2.0.md ✅ Finalized
ROADMAP.md ✅ Created
docs/releases/README.md ✅ Updated
docs/README.md ✅ v1.2.0 index
CHANGELOG.md ✅ [1.2.0] section
docs/adr/README.md ✅ Platform ADR overview
CONTRIBUTING.md ✅ ADR range + install reference

Architecture consistency

Check Result
Interface → Facade → Workflow diagram ✅ Consistent across README, ARCHITECTURE, CURRENT_STATUS
Discovery + Execution Planning in pipeline
Canonical artifacts documented ✅ Implemented vs planned distinguished
GitHub Provider scope (no clone)

README review

Check Result
CLI as primary entry
SDK examples
app.py demoted to maintainer notes
Version 1.2.0
Roadmap link

Getting Started review

Check Result
init → doctor → reproduce flow
No app.py as primary
SDK section

Roadmap review

Check Result
v1.0–v1.2 completed
v1.3–v1.5 planned
Future interfaces marked not implemented

Release Notes review

Check Result
Highlights complete
Migration guide
Breaking changes documented

Terminology consistency

Term Consistent
Execution Planning (not "Execution Planner")
Research Resource Discovery / Discovery
ExecutionStrategy
Platform Facade / Man1Lab
ResearchResourceDiscovery

Diagram consistency

Check Result
No v1.1-only pipeline without Discovery
Interface layer shown

Outdated content removed

Item Status
v1.1.0 as current version in README citation ✅ Fixed → 1.2.0
app.py as recommended quick start ✅ Removed from user paths
docs/README v1.1.0 header ✅ Updated
ARCHITECTURE "Repository discovery planned" in §6 ✅ Updated — Discovery complete

Remaining documentation debt

Item Notes
docs/architecture/CAPABILITIES.md Per-agent detail; not fully refreshed in this freeze
docs/api/README.md Partial refresh — facade as primary entry
ADR-0013/0014/0016 status still Draft Promote to Accepted at release tag
DEVELOPMENT.md Maintainer doc; partial interface table may need sync
Benchmark table dates Historical M8.x runs unchanged
Future MCP/REST Correctly marked not implemented

Verdict

Documentation Ready for Man1Lab v1.2.0 Release