diff --git a/activity-definitions/hfact-glas-metered-proof.md b/activity-definitions/hfact-glas-metered-proof.md new file mode 100644 index 0000000..c11debc --- /dev/null +++ b/activity-definitions/hfact-glas-metered-proof.md @@ -0,0 +1,41 @@ +--- +id: hfact-glas-metered-proof +name: HelixForge Glas Metered Proof +enabled: false +owner: activity-core +governance: custodian +status: proposed +trigger: + type: scheduled + at: "2099-01-01T00:00:00Z" + timezone: UTC +--- + +# HelixForge Glas Metered Proof + +Disabled, operator-triggered paid proof for SECRETS-WP-0009-T03 / +GLAS-WP-0012-T04 / HFACT-WP-0001-T04. It emits exactly one bounded task into the +disposable `hfact-glas-proof` repository on railiance01. Only the spend-admitted +`rein-aharness metered-once` owner claims it: the label `hfact-metered` is not +claimed by the `automated` claim loop. The far-future timestamp is only a valid +definition shape; disabled status prevents any schedule. + +```rule +id: execute-hfact-glas-metered-proof +condition: "True" +action: + task_template: Record the HelixForge Glas metered proof + description: 'Within hfact-glas-proof only, create PROOF.md containing exactly the line "HelixForge Glas metered proof: ok". Commit exactly that file with message "proof: record Glas metered run". Do not push or change any external system.' + target_repo: hfact-glas-proof + priority: low + labels: ["hfact-metered"] + harness_profile_ref: harness.agent-dev-local@1.1.1 + execution_refs: + correlation_id: SECRETS-WP-0009-T03 + assignment_ref: HFACT-WP-0001-T04 + repository_grant: + version: "1" + allowed_paths: [PROOF.md] + commit_count: {min: 1, max: 1} + publish: false +``` diff --git a/k8s/railiance/20-runtime.yaml b/k8s/railiance/20-runtime.yaml index ed7a48e..8568145 100644 --- a/k8s/railiance/20-runtime.yaml +++ b/k8s/railiance/20-runtime.yaml @@ -123,6 +123,48 @@ data: correlation_id: ACTIVITY-WP-0032-T05 assignment_ref: ACTIVITY-WP-0032-T05 ``` + hfact-glas-metered-proof.md: | + --- + id: hfact-glas-metered-proof + name: HelixForge Glas Metered Proof + enabled: false + owner: activity-core + governance: custodian + status: proposed + trigger: + type: scheduled + at: "2099-01-01T00:00:00Z" + timezone: UTC + --- + + # HelixForge Glas Metered Proof + + Disabled, operator-triggered paid proof for SECRETS-WP-0009-T03 / + GLAS-WP-0012-T04 / HFACT-WP-0001-T04. It emits exactly one bounded task into the + disposable `hfact-glas-proof` repository on railiance01. Only the spend-admitted + `rein-aharness metered-once` owner claims it: the label `hfact-metered` is not + claimed by the `automated` claim loop. The far-future timestamp is only a valid + definition shape; disabled status prevents any schedule. + + ```rule + id: execute-hfact-glas-metered-proof + condition: "True" + action: + task_template: Record the HelixForge Glas metered proof + description: 'Within hfact-glas-proof only, create PROOF.md containing exactly the line "HelixForge Glas metered proof: ok". Commit exactly that file with message "proof: record Glas metered run". Do not push or change any external system.' + target_repo: hfact-glas-proof + priority: low + labels: ["hfact-metered"] + harness_profile_ref: harness.agent-dev-local@1.1.1 + execution_refs: + correlation_id: SECRETS-WP-0009-T03 + assignment_ref: HFACT-WP-0001-T04 + repository_grant: + version: "1" + allowed_paths: [PROOF.md] + commit_count: {min: 1, max: 1} + publish: false + ``` daily-sbom-catchup.md: | --- id: daily-sbom-catchup