devagent-physical-engine 1.4.0__tar.gz → 1.5.0__tar.gz

{devagent_physical_engine-1.4.0/src/devagent_physical_engine.egg-info → devagent_physical_engine-1.5.0}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: devagent-physical-engine
-Version: 1.4.0
-Summary: Production-grade verification-first robotics evidence runtime with one-command customer intake, selective verification execution, deterministic Twin lineage, measured physical verification, replay inspection, regression, and FAT evidence.
+Version: 1.5.0
+Summary: Production-grade verification-first robotics evidence runtime with one-command customer intake, validated requirement mapping, requirement-driven test generation, selective verification, deterministic Twin lineage, measured physical verification, replay inspection, regression, and FAT evidence.
 Author: Tom Ha
 License: All Rights Reserved
 Project-URL: Homepage, https://github.com/tomha85/devagent-physical-engine
@@ -58,15 +58,17 @@ requirements + explicit engineering facts
     ↓
 immutable Digital Twin revision
     ↓
-deterministic verification plan
+validated Requirement → Criterion mapping
+    ↓
+requirement-driven nominal / boundary / fault cases
     ↓
 measured evidence when a qualified execution path exists
     ↓
 PASS / FAIL / NOT_TESTED
     ↓
-FAT report + Evidence Viewer
+regression + FAT report + Evidence Viewer
     ↓
-selective retest / replay / regression
+selective retest / replay
 ```
 
 > **AI proposes. Deterministic engines validate, compile, verify, measure, and gate promotion. OEM robot controllers, PLCs, safety PLCs, and certified safety systems remain authoritative.**
@@ -80,7 +82,7 @@ DevAgent is designed to answer: **What can be proven about this cell, what faile
 Python 3.11+ is required.
 
 ```bash
-python -m pip install --upgrade devagent-physical-engine==1.4.0
+python -m pip install --upgrade devagent-physical-engine==1.5.0
 ```
 
 Verify the package:
@@ -92,7 +94,7 @@ python -c "import devagent_physical_engine as d; print(d.__version__)"
 Expected:
 
 ```text
-1.4.0
+1.5.0
 ```
 
 Run the normal customer workflow:
@@ -119,7 +121,7 @@ For machine-readable CI output:
 devagent verify ./customer-project --json
 ```
 
-Simple Mode automatically handles project identity, customer-file inventory, supported XLSX requirement normalization, bounded Twin normalization, deterministic campaign generation, FAT generation, and evidence rendering. The user does not need to manually manage artifact IDs for the normal workflow.
+Simple Mode automatically handles project identity, customer-file inventory, supported XLSX requirement normalization, bounded Twin normalization, validated requirement mapping, requirement-driven test generation, deterministic campaign generation, regression/FAT generation, and evidence rendering. The user does not need to manually manage artifact IDs for the normal workflow.
 
 Default locations:
 
@@ -175,23 +177,25 @@ Update the original customer engineering information and rerun the same command.
 
 # What the terminal shows
 
-Human Simple Mode keeps the terminal as the primary progress surface:
+Human Simple Mode keeps the terminal as the primary progress surface. v1.5 distinguishes generated/recorded artifacts from executed evidence:
 
 ```text
 [DevAgent +   0.00s] START         RUNNING    source=ACME_CNC_CELL_TEST
 [DevAgent +   0.00s] INTAKE        RUNNING    scanning and classifying customer engineering files
-[DevAgent +   0.42s] REQUIREMENTS  READY      customer requirements normalized
+[DevAgent +   0.42s] REQUIREMENTS  MAPPED     mapped=8/17 unmapped=9
 [DevAgent +   0.61s] TWIN          NORMALIZED customer Twin draft normalized
 [DevAgent +   0.85s] PROJECT       READY      project_id=acme-cell
-[DevAgent +   0.91s] PLAN          READY      artifact=...
+[DevAgent +   0.91s] PLAN          GENERATED  physical_cases=7 mapped_checks=8/17
 [DevAgent +   1.02s] SIMULATION    BLOCKED    imported_customer_twin_execution_adapter_not_yet_qualified
-[DevAgent +   1.11s] CAMPAIGN      COMPLETE   artifact=...
-[DevAgent +   1.18s] FAT           COMPLETE   artifact=...
-[DevAgent +   1.24s] EVIDENCE      COMPLETE   bundle=...
+[DevAgent +   1.11s] CAMPAIGN      RECORDED   tests=8/17 verdict=INCONCLUSIVE
+[DevAgent +   1.18s] FAT           GENERATED  decision=INCONCLUSIVE
+[DevAgent +   1.24s] EVIDENCE      GENERATED  scope=MODEL_ONLY
 [DevAgent +   1.25s] COMPLETE      DONE       state=verification_incomplete release_ready=False real_execution_allowed=False
 [DevAgent +   1.25s] REPORT        OPENING    new tab requested; terminal remains active
 ```
 
+When a separately qualified exact-Twin simulation executor provides validated physical measurements, evidence scope can advance to `SIMULATION_MEASURED`. A generated plan or AI proposal alone never does that.
+
 Progress is also persisted to:
 
 ```text
@@ -204,6 +208,56 @@ Use `--no-progress` to suppress human progress. `--json` remains machine-clean a
 
 ---
 
+# v1.5 commercial intelligence
+
+v1.5 adds a bounded Commercial Intelligence layer above the existing deterministic authority model.
+
+The new requirement path is:
+
+```text
+customer requirement prose / explicit check
+    ↓
+deterministic semantic proposal and optional provider-backed proposal
+    ↓
+RequirementCriterionValidator
+    ↓
+accepted executable criterion OR engineer confirmation required
+```
+
+High-confidence deterministic mappings include explicit cycle-time limits, minimum clearance, TCP error, tracking error, no-collision language, and physical completion language. Numeric units are normalized before becoming executable criteria.
+
+Provider-backed OpenAI / Anthropic / Gemini proposals are advisory. A provider proposal cannot create physical truth, site qualification, or real-execution authority. Unsupported, low-confidence, malformed, or non-corroborated proposals remain unaccepted and require confirmation.
+
+Requirement-driven case generation can derive bounded variations and fault cases from explicit engineering requirements, including payload boundaries, TCP offset boundaries, missing-workpiece faults, and grasp-verification failures. Requirement → Case mapping is persisted as immutable evidence.
+
+The full commercial orchestration order is intentionally:
+
+```text
+requirements
+    ↓
+validated criteria
+    ↓
+verification cases
+    ↓
+exact Twin
+    ↓
+qualified simulation if available
+    ↓
+typed physical measurement
+    ↓
+campaign verdicts
+    ↓
+repeat-run regression
+    ↓
+FAT + evidence bundle
+```
+
+A `QualifiedSimulationExecutor` must persist exact-Twin typed measurement evidence. One-Command revalidates the returned artifact before measurement is allowed to influence requirement verdicts. If no qualified arbitrary-customer execution adapter exists, simulation stays blocked and physical requirements stay `NOT_TESTED`.
+
+Repeat runs on the same project can automatically compare the previous and current campaign and record regression evidence before generating the new FAT artifact.
+
+---
+
 # Interactive engineering session
 
 With `--open` in a real TTY, or with explicit `--interactive`, DevAgent keeps a bounded engineering prompt after the full verification run:
@@ -720,18 +774,23 @@ Existing certified controllers execute.
 
 # Project status
 
-**v1.4.0 — Production/Stable software workflow**
+**v1.5.0 — Production/Stable software workflow**
 
-v1.4.0 adds selective verification execution while preserving the existing fail-closed authority model.
+v1.5.0 adds validated Requirement → Criterion intelligence, requirement-driven boundary/fault case generation, qualified simulation measurement binding contracts, clearer customer-facing progress semantics, and automatic repeat-run regression orchestration while preserving fail-closed authority.
 
 Production-oriented software capabilities include:
 
 ```text
 one-command customer intake
 XLSX requirement normalization
+validated Requirement → Criterion mapping
+optional provider-backed criterion proposals with deterministic validation
+requirement-driven nominal / boundary / fault case generation
 immutable project/Twin lineage
 deterministic full campaigns
+qualified simulation measurement binding contract
 measured evidence binding
+repeat-run regression orchestration
 professional FAT/Evidence Viewer
 terminal progress + RUN.log
 interactive engineering session
@@ -745,7 +804,7 @@ change impact + regression
 provider-neutral optional AI front end
 ```
 
-Quality gates include Python 3.11/3.12/3.13 regression, package clean-install, dependency audit, global branch coverage, One-Command coverage, **Selective Verification coverage**, Production Authority coverage, and Evidence Trust/Replay coverage.
+Quality gates include Python 3.11/3.12/3.13 regression, package clean-install, dependency audit, global branch coverage, One-Command coverage, **Commercial Intelligence coverage**, **Selective Verification coverage**, Production Authority coverage, and Evidence Trust/Replay coverage.
 
 Production/Stable describes the bounded software workflow. It does not claim arbitrary customer cells are physically qualified, site-qualified, or safe for autonomous real execution.
 

{devagent_physical_engine-1.4.0 → devagent_physical_engine-1.5.0}/README.md

@@ -17,15 +17,17 @@ requirements + explicit engineering facts
     ↓
 immutable Digital Twin revision
     ↓
-deterministic verification plan
+validated Requirement → Criterion mapping
+    ↓
+requirement-driven nominal / boundary / fault cases
     ↓
 measured evidence when a qualified execution path exists
     ↓
 PASS / FAIL / NOT_TESTED
     ↓
-FAT report + Evidence Viewer
+regression + FAT report + Evidence Viewer
     ↓
-selective retest / replay / regression
+selective retest / replay
 ```
 
 > **AI proposes. Deterministic engines validate, compile, verify, measure, and gate promotion. OEM robot controllers, PLCs, safety PLCs, and certified safety systems remain authoritative.**
@@ -39,7 +41,7 @@ DevAgent is designed to answer: **What can be proven about this cell, what faile
 Python 3.11+ is required.
 
 ```bash
-python -m pip install --upgrade devagent-physical-engine==1.4.0
+python -m pip install --upgrade devagent-physical-engine==1.5.0
 ```
 
 Verify the package:
@@ -51,7 +53,7 @@ python -c "import devagent_physical_engine as d; print(d.__version__)"
 Expected:
 
 ```text
-1.4.0
+1.5.0
 ```
 
 Run the normal customer workflow:
@@ -78,7 +80,7 @@ For machine-readable CI output:
 devagent verify ./customer-project --json
 ```
 
-Simple Mode automatically handles project identity, customer-file inventory, supported XLSX requirement normalization, bounded Twin normalization, deterministic campaign generation, FAT generation, and evidence rendering. The user does not need to manually manage artifact IDs for the normal workflow.
+Simple Mode automatically handles project identity, customer-file inventory, supported XLSX requirement normalization, bounded Twin normalization, validated requirement mapping, requirement-driven test generation, deterministic campaign generation, regression/FAT generation, and evidence rendering. The user does not need to manually manage artifact IDs for the normal workflow.
 
 Default locations:
 
@@ -134,23 +136,25 @@ Update the original customer engineering information and rerun the same command.
 
 # What the terminal shows
 
-Human Simple Mode keeps the terminal as the primary progress surface:
+Human Simple Mode keeps the terminal as the primary progress surface. v1.5 distinguishes generated/recorded artifacts from executed evidence:
 
 ```text
 [DevAgent +   0.00s] START         RUNNING    source=ACME_CNC_CELL_TEST
 [DevAgent +   0.00s] INTAKE        RUNNING    scanning and classifying customer engineering files
-[DevAgent +   0.42s] REQUIREMENTS  READY      customer requirements normalized
+[DevAgent +   0.42s] REQUIREMENTS  MAPPED     mapped=8/17 unmapped=9
 [DevAgent +   0.61s] TWIN          NORMALIZED customer Twin draft normalized
 [DevAgent +   0.85s] PROJECT       READY      project_id=acme-cell
-[DevAgent +   0.91s] PLAN          READY      artifact=...
+[DevAgent +   0.91s] PLAN          GENERATED  physical_cases=7 mapped_checks=8/17
 [DevAgent +   1.02s] SIMULATION    BLOCKED    imported_customer_twin_execution_adapter_not_yet_qualified
-[DevAgent +   1.11s] CAMPAIGN      COMPLETE   artifact=...
-[DevAgent +   1.18s] FAT           COMPLETE   artifact=...
-[DevAgent +   1.24s] EVIDENCE      COMPLETE   bundle=...
+[DevAgent +   1.11s] CAMPAIGN      RECORDED   tests=8/17 verdict=INCONCLUSIVE
+[DevAgent +   1.18s] FAT           GENERATED  decision=INCONCLUSIVE
+[DevAgent +   1.24s] EVIDENCE      GENERATED  scope=MODEL_ONLY
 [DevAgent +   1.25s] COMPLETE      DONE       state=verification_incomplete release_ready=False real_execution_allowed=False
 [DevAgent +   1.25s] REPORT        OPENING    new tab requested; terminal remains active
 ```
 
+When a separately qualified exact-Twin simulation executor provides validated physical measurements, evidence scope can advance to `SIMULATION_MEASURED`. A generated plan or AI proposal alone never does that.
+
 Progress is also persisted to:
 
 ```text
@@ -163,6 +167,56 @@ Use `--no-progress` to suppress human progress. `--json` remains machine-clean a
 
 ---
 
+# v1.5 commercial intelligence
+
+v1.5 adds a bounded Commercial Intelligence layer above the existing deterministic authority model.
+
+The new requirement path is:
+
+```text
+customer requirement prose / explicit check
+    ↓
+deterministic semantic proposal and optional provider-backed proposal
+    ↓
+RequirementCriterionValidator
+    ↓
+accepted executable criterion OR engineer confirmation required
+```
+
+High-confidence deterministic mappings include explicit cycle-time limits, minimum clearance, TCP error, tracking error, no-collision language, and physical completion language. Numeric units are normalized before becoming executable criteria.
+
+Provider-backed OpenAI / Anthropic / Gemini proposals are advisory. A provider proposal cannot create physical truth, site qualification, or real-execution authority. Unsupported, low-confidence, malformed, or non-corroborated proposals remain unaccepted and require confirmation.
+
+Requirement-driven case generation can derive bounded variations and fault cases from explicit engineering requirements, including payload boundaries, TCP offset boundaries, missing-workpiece faults, and grasp-verification failures. Requirement → Case mapping is persisted as immutable evidence.
+
+The full commercial orchestration order is intentionally:
+
+```text
+requirements
+    ↓
+validated criteria
+    ↓
+verification cases
+    ↓
+exact Twin
+    ↓
+qualified simulation if available
+    ↓
+typed physical measurement
+    ↓
+campaign verdicts
+    ↓
+repeat-run regression
+    ↓
+FAT + evidence bundle
+```
+
+A `QualifiedSimulationExecutor` must persist exact-Twin typed measurement evidence. One-Command revalidates the returned artifact before measurement is allowed to influence requirement verdicts. If no qualified arbitrary-customer execution adapter exists, simulation stays blocked and physical requirements stay `NOT_TESTED`.
+
+Repeat runs on the same project can automatically compare the previous and current campaign and record regression evidence before generating the new FAT artifact.
+
+---
+
 # Interactive engineering session
 
 With `--open` in a real TTY, or with explicit `--interactive`, DevAgent keeps a bounded engineering prompt after the full verification run:
@@ -679,18 +733,23 @@ Existing certified controllers execute.
 
 # Project status
 
-**v1.4.0 — Production/Stable software workflow**
+**v1.5.0 — Production/Stable software workflow**
 
-v1.4.0 adds selective verification execution while preserving the existing fail-closed authority model.
+v1.5.0 adds validated Requirement → Criterion intelligence, requirement-driven boundary/fault case generation, qualified simulation measurement binding contracts, clearer customer-facing progress semantics, and automatic repeat-run regression orchestration while preserving fail-closed authority.
 
 Production-oriented software capabilities include:
 
 ```text
 one-command customer intake
 XLSX requirement normalization
+validated Requirement → Criterion mapping
+optional provider-backed criterion proposals with deterministic validation
+requirement-driven nominal / boundary / fault case generation
 immutable project/Twin lineage
 deterministic full campaigns
+qualified simulation measurement binding contract
 measured evidence binding
+repeat-run regression orchestration
 professional FAT/Evidence Viewer
 terminal progress + RUN.log
 interactive engineering session
@@ -704,7 +763,7 @@ change impact + regression
 provider-neutral optional AI front end
 ```
 
-Quality gates include Python 3.11/3.12/3.13 regression, package clean-install, dependency audit, global branch coverage, One-Command coverage, **Selective Verification coverage**, Production Authority coverage, and Evidence Trust/Replay coverage.
+Quality gates include Python 3.11/3.12/3.13 regression, package clean-install, dependency audit, global branch coverage, One-Command coverage, **Commercial Intelligence coverage**, **Selective Verification coverage**, Production Authority coverage, and Evidence Trust/Replay coverage.
 
 Production/Stable describes the bounded software workflow. It does not claim arbitrary customer cells are physically qualified, site-qualified, or safe for autonomous real execution.
 

{devagent_physical_engine-1.4.0 → devagent_physical_engine-1.5.0}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "devagent-physical-engine"
-version = "1.4.0"
-description = "Production-grade verification-first robotics evidence runtime with one-command customer intake, selective verification execution, deterministic Twin lineage, measured physical verification, replay inspection, regression, and FAT evidence."
+version = "1.5.0"
+description = "Production-grade verification-first robotics evidence runtime with one-command customer intake, validated requirement mapping, requirement-driven test generation, selective verification, deterministic Twin lineage, measured physical verification, replay inspection, regression, and FAT evidence."
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.11"
 dependencies = ["PyYAML>=6.0,<7"]
@@ -47,7 +47,7 @@ Repository = "https://github.com/tomha85/devagent-physical-engine"
 Issues = "https://github.com/tomha85/devagent-physical-engine/issues"
 
 [project.scripts]
-devagent = "devagent_physical_engine.user_cli:main"
+devagent = "devagent_physical_engine.user_cli_v15:main"
 devagent-physical = "devagent_physical_engine.cli:main"
 devagent-physical-ai = "devagent_physical_engine.ai_cli:main"
 devagent-commercial = "devagent_physical_engine.commercial_cli:main"

{devagent_physical_engine-1.4.0 → devagent_physical_engine-1.5.0}/src/devagent_physical_engine/__init__.py

@@ -9,6 +9,21 @@ from .commercial import (
 )
 from .commercial_campaign import CommercialCampaignRunner, record_requirement_set
 from .commercial_importer import CustomerTwinImporter
+from .commercial_intelligence import (
+    COMMERCIAL_INTELLIGENCE_SCHEMA_VERSION,
+    CommercialIntelligenceRecorder,
+    CriterionProposal,
+    CriterionProposalProvider,
+    DeterministicSemanticCriterionProposer,
+    MappingIssue,
+    QualifiedSimulationExecutor,
+    RequirementCasePlan,
+    RequirementCriterionMapper,
+    RequirementCriterionValidator,
+    RequirementDrivenCasePlanner,
+    RequirementMappingResult,
+    SimulationExecutionReceipt,
+)
 from .commercial_readiness import CommercialProjectStatus, FATReportBuilder
 from .commercial_repository import CommercialProjectRepository
 from .evidence_replay import ReplayInspectionService
@@ -33,9 +48,9 @@ from .one_command import (
     IntakeFile,
     IntakeQuestion,
     OneCommandError,
-    OneCommandVerifier,
-    SimpleVerifyResult,
 )
+from .one_command_runtime import install_one_command_runtime
+from .one_command_v15 import OneCommandVerifier, SimpleVerifyResult
 from .physical_motion import JointTrajectoryPoint, MotionExecutionMetrics, PhysicalMotionPlan
 from .production_authority import (
     PhysicalEvidenceRecorder,
@@ -59,6 +74,12 @@ from .project import (
     SQLiteProjectRepository,
     TwinRevisionRecord,
 )
+from .provider_criterion import (
+    PROVIDER_CRITERION_SCHEMA_VERSION,
+    ProviderCriterionConfig,
+    ProviderCriterionProposer,
+    StructuredCriterionProvider,
+)
 from .robot_platform import (
     BUILTIN_ROBOT_PROFILES,
     QualificationState,
@@ -138,6 +159,23 @@ __all__ = [
     "OneCommandError",
     "OneCommandVerifier",
     "SimpleVerifyResult",
+    "COMMERCIAL_INTELLIGENCE_SCHEMA_VERSION",
+    "CommercialIntelligenceRecorder",
+    "CriterionProposal",
+    "CriterionProposalProvider",
+    "DeterministicSemanticCriterionProposer",
+    "MappingIssue",
+    "QualifiedSimulationExecutor",
+    "RequirementCasePlan",
+    "RequirementCriterionMapper",
+    "RequirementCriterionValidator",
+    "RequirementDrivenCasePlanner",
+    "RequirementMappingResult",
+    "SimulationExecutionReceipt",
+    "PROVIDER_CRITERION_SCHEMA_VERSION",
+    "ProviderCriterionConfig",
+    "ProviderCriterionProposer",
+    "StructuredCriterionProvider",
     "SELECTIVE_VERIFICATION_SCHEMA_VERSION",
     "RequirementTestResolver",
     "ResolvedVerificationSelection",
@@ -149,4 +187,6 @@ __all__ = [
     "VerificationTestMappingRecorder",
 ]
 
-__version__ = "1.4.0"
+install_one_command_runtime()
+
+__version__ = "1.5.0"