@tomflow/proflow-execution-contracts
v0.1.14
Published
Typed public Execution contracts and runtime validation for the ProFlow real-world effect plane.
Maintainers
Readme
@tomflow/proflow-execution-contracts
Typed public Execution contracts and runtime validation for the ProFlow real-world effect plane.
Normative source: spec/执行领域/02-契约/01-Public-Contract与TypeScript类型规范.md.
v1 Journey contract alignment
The public contract keeps stable business refs separate from transient Browser runtime identity and now treats ArtifactRef and EvidenceRef as different semantics. It exposes no WorkerTurn/Observer store contract and no frame/persistent-tab business identity.
Monitor Browser effects use effect.execute({effectId, action, payload}) (POST /effects/execute). parseMonitorEffectRequest validates the existing capability payload and requires payload.driveId === effectId; parseMonitorEffectReceipt returns only PENDING/APPLIED/NOT_APPLIED and a typed result for APPLIED. The Execution SQLite row remains the sole durable owner.
browser.action extends the same effect contract with RELOAD and observation-only CAPTURE. It preserves driveId, uses the existing Runtime executions row, and returns loaded runtime/version or DOM evidence; it is not a second effect owner.
