| name | law-policy-creater |
| description | Create law-policy/v0.5.4 files for current ArchSig measurement runs. |
LawPolicy Creater
Use this skill to create a law-policy/v0.5.4 file, a separate
measurement-profile/v0.5.4 file, and a law-equation-surface/v0.5.4 /
archsig-policy-bundle/v0.5.4 input set for an AG run.
Workflow
- Select evaluator manifests and laws from the current registry.
- Select one external MeasurementProfile artifact and one law-equation-surface artifact for the run.
- Record
basisLedger entries and policy basis refs.
- Validate with
archsig measurement-profile --measurement-profile <profile> --out <report>.
- Validate with
archsig law-policy --law-policy <policy> --measurement-profile <profile> --law-surface <law-surface> --out <report>.
- Create and validate a bundle with
archsig policy-bundle --law-policy <policy> --law-surface <law-surface> --measurement-profile <profile> --out <bundle>.
- Run
archsig analyze --archmap <archmap> --policy-bundle <bundle> --out-dir <run-dir>.
For the executable fixture workflow, use
references/schema-guide.md and references/law-surface-examples.md.
For ag.law-conflict-tor, use an explicit policies[].lawPair with exactly two
distinct law ids; law-id naming conventions are not selectors.
The bundle is the reproducibility record: its three component references and
canonical fingerprints must be preserved with the run.
Gate decisions belong in archsig gate policy, not in analyze flags.
For ag.saga-grounded, author quotientSheafCondition on the law-equation
surface. The selected law also
requires the law's witnessVariables and forbiddenSupportGenerators; these
generate the finite quotient and cannot be replaced by conclusion fields.
Compare class-zero transport is derived from the selected normalized ArchMap
cover/context relation; do not author a separate transport artifact.
