activity-core/activity-definitions/hfact-glas-metered-proof.md
tegwick 6002d5c5f6 Add disabled hfact-glas-metered-proof definition
Operator-triggered paid proof for SECRETS-WP-0009-T03 / HFACT-WP-0001-T04.
Label hfact-metered keeps it away from the automated claim loop; grant
limits the run to PROOF.md and one local commit. Profile
harness.agent-dev-local@1.1.1 (claude-sonnet-5).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 226514@bnt-lap001
Assistant-Session: 26ba103d-05fe-45a1-9cd7-9475bf239df6
2026-09-23 17:00:52 +02:00

1.4 KiB

id name enabled owner governance status trigger
hfact-glas-metered-proof HelixForge Glas Metered Proof false activity-core custodian proposed
type at timezone
scheduled 2099-01-01T00:00:00Z 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.

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