Method / execution governance

Make the boundary inspectable.

Public Contract distinguishes what a system proposes, what its declared checks establish, and what is authorized to change state. Those stages are deliberately not treated as interchangeable.

Contract first

Declare the object under inspection, expected behavior, comparison rule, source constraints and permitted operations before treating an output as a result.

Deterministic evaluation

Run bounded technical checks against the declared envelope; capture relevant differences, uncertainties and failure cases rather than inferring an unrestricted guarantee.

Evidence and replay

Generate local receipts, retain traceable inputs and methods, and preserve the distinction between a replayable technical observation and an independently accepted finding.

Separate authority

A technical OPEN signal does not constitute regulatory approval, a signed legal opinion, an authorized production deployment or an external certificate.

Which route fits the question?

Forge explains the execution model; Verify compares artifacts under selected profiles; Compliance examines applicability and review conditions. The shared workstation view keeps their navigation together without blending their engines or evidence ledgers.