← TelarchCONTENT HISTORY

Update to Telarch

Snapshot Nov 17, 2026 · 00:13 UTC · version 0.2.2

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for telarch-attest

Full description — Now says: Use when sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Telarch and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Nov 16, 2026 · 18:16 UTC

Use when verifying Telarch computation cards or receipts. Verify OKF Attested Computation sidecars and Argus receipt bindings.

After

Nov 17, 2026 · 00:13 UTC

Use when sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits.

Skill instructions

Before

Nov 16, 2026 · 18:16 UTC

verifying Telarch computation cards or receipts. Verify OKF Attested Computation sidecars and Argus receipt bindings. # Telarch Attestation Verification Verify deterministic computation attestations, OKF sidecar cards, and Argus audit le...

After

Nov 17, 2026 · 00:13 UTC

sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits. # Telarch Audit Chains (hosted server) Seal events into a SHA-256 hash chain and verify a chain that is passed in. Th...

Supporting files

Before

Nov 16, 2026 · 18:16 UTC

[{"relative_path":"references/cards.md","size_in_bytes":1197},{"relative_path":"references/verification.md","size_in_bytes":961}]

After

Nov 17, 2026 · 00:13 UTC

[{"relative_path":"references/verification.md","size_in_bytes":1158}]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,20 +1,20 @@
 ---
 name: telarch-attest
-description: Use when verifying Telarch computation cards or receipts. Verify OKF Attested Computation sidecars and Argus receipt bindings.
+description: Use when sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits.
 ---
 
-# Telarch Attestation Verification
+# Telarch Audit Chains (hosted server)
 
-Verify deterministic computation attestations, OKF sidecar cards, and Argus audit ledger bindings.
+Seal events into a SHA-256 hash chain and verify a chain that is passed in. The hosted server stores no ledger: the chain lives with the caller.
 
 ## Operational Rules
 
-1. **Deterministic and Offline**: Never invoke remote networks or LLMs for attestation verification.
-2. **Bidirectional Binding**: Always verify both directions: the battery references the receipt sequence, and the receipt payload embeds the SHA-256 hashes of the battery and its card sidecar.
-3. **Chain Continuity**: Confirm Argus ledger cryptographic hash chain verification passes up to the receipt sequence.
-4. **Git Tree Verification**: Confirm computation entrypoint digest matches the recorded Git commit tree object.
+1. **Seal**: `argus_audit_seal` takes `events` (each with `event_type`, `actor` and `payload`) and returns them with `sequence`, `event_id`, `timestamp`, `canonical_payload`, `prev_hash` and `event_hash`, plus `head_hash`. An event sent without a `timestamp` comes back with `timestamp: null`.
+2. **Integers only**: a payload with a non-integer number is refused (`FloatPayloadError`), and so is an integer beyond 2**53 - 1 (`UnsafeIntegerError`). Use basis points or strings.
+3. **Continue a chain**: pass the previous `head_hash` as `prev_hash` and give the first event its `sequence`.
+4. **Verify**: `argus_audit_verify` takes the sealed `events` and recomputes every hash. It returns `valid`, `total_events`, `head_hash`, `anchor_prev_hash`, `starts_at_genesis` and, when broken, `first_broken_index`, `first_broken_sequence` and `error_detail`.
+5. **Say what was proven**: `valid: true` means the events passed in are consistent with each other from `anchor_prev_hash` on. It proves the chain is complete only when `starts_at_genesis` is true and the caller compares `head_hash` with a value kept elsewhere.
 
 ## Supporting References
 
-- See [Attested Computation Cards Specification](references/cards.md) for OKF §10.2 schema rules.
-- See [Verification Guide](references/verification.md) for offline verification instructions.
+- See [Verification Guide](references/verification.md).
Full technical diff · 3 changed fields

changed /description

BEFORE
"Use when verifying Telarch computation cards or receipts. Verify OKF Attested Computation sidecars and Argus receipt bindings."
AFTER
"Use when sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits."

changed /included_files

BEFORE
[
  {
    "relative_path": "references/cards.md",
    "size_in_bytes": 1197
  },
  {
    "relative_path": "references/verification.md",
    "size_in_bytes": 961
  }
]
AFTER
[
  {
    "relative_path": "references/verification.md",
    "size_in_bytes": 1158
  }
]

changed /skill_md_contents

BEFORE
"---\nname: telarch-attest\ndescription: Use when verifying Telarch computation cards or receipts. Verify OKF Attested Computation sidecars and Argus receipt bindings.\n---\n\n# Telarch Attestation Verification\n\nVerify deterministic computation attestations, OKF sidecar cards, and Argus audit ledger bindings.\n\n## Operational Rules\n\n1. **Deterministic and Offline**: Never invoke remote networks or LLMs for attestation verification.\n2. **Bidirectional Binding**: Always verify both directions: the battery references the receipt sequence, and the receipt payload embeds the SHA-256 hashes of the battery and its card sidecar.\n3. **Chain Continuity**: Confirm Argus ledger cryptographic hash chain verification passes up to the receipt sequence.\n4. **Git Tree Verification**: Confirm computation entrypoint digest matches the recorded Git commit tree object.\n\n## Supporting References\n\n- See [Attested Computation Cards Specification](references/cards.md) for OKF §10.2 schema rules.\n- See [Verification Guide](references/verification.md) for offline verification instructions.\n"
AFTER
"---\nname: telarch-attest\ndescription: Use when sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits.\n---\n\n# Telarch Audit Chains (hosted server)\n\nSeal events into a SHA-256 hash chain and verify a chain that is passed in. The hosted server stores no ledger: the chain lives with the caller.\n\n## Operational Rules\n\n1. **Seal**: `argus_audit_seal` takes `events` (each with `event_type`, `actor` and `payload`) and returns them with `sequence`, `event_id`, `timestamp`, `canonical_payload`, `prev_hash` and `event_hash`, plus `head_hash`. An event sent without a `timestamp` comes back with `timestamp: null`.\n2. **Integers only**: a payload with a non-integer number is refused (`FloatPayloadError`), and so is an integer beyond 2**53 - 1 (`UnsafeIntegerError`). Use basis points or strings.\n3. **Continue a chain**: pass the previous `head_hash` as `prev_hash` and give the first event its `sequence`.\n4. **Verify**: `argus_audit_verify` takes the sealed `events` and recomputes every hash. It returns `valid`, `total_events`, `head_hash`, `anchor_prev_hash`, `starts_at_genesis` and, when broken, `first_broken_index`, `first_broken_sequence` and `error_detail`.\n5. **Say what was proven**: `valid: true` means the events passed in are consistent with each other from `anchor_prev_hash` on. It proves the chain is complete only when `starts_at_genesis` is true and the caller compares `head_hash` with a value kept elsewhere.\n\n## Supporting References\n\n- See [Verification Guide](references/verification.md).\n"
Full snapshot data
{
  "description": "Use when sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits.",
  "included_files": [
    {
      "relative_path": "references/verification.md",
      "size_in_bytes": 1158
    }
  ],
  "name": "telarch-attest",
  "skill_md_contents": "---\nname: telarch-attest\ndescription: Use when sealing or verifying an Argus SHA-256 audit chain. Seal a list of events into a hash chain and check a chain for edits.\n---\n\n# Telarch Audit Chains (hosted server)\n\nSeal events into a SHA-256 hash chain and verify a chain that is passed in. The hosted server stores no ledger: the chain lives with the caller.\n\n## Operational Rules\n\n1. **Seal**: `argus_audit_seal` takes `events` (each with `event_type`, `actor` and `payload`) and returns them with `sequence`, `event_id`, `timestamp`, `canonical_payload`, `prev_hash` and `event_hash`, plus `head_hash`. An event sent without a `timestamp` comes back with `timestamp: null`.\n2. **Integers only**: a payload with a non-integer number is refused (`FloatPayloadError`), and so is an integer beyond 2**53 - 1 (`UnsafeIntegerError`). Use basis points or strings.\n3. **Continue a chain**: pass the previous `head_hash` as `prev_hash` and give the first event its `sequence`.\n4. **Verify**: `argus_audit_verify` takes the sealed `events` and recomputes every hash. It returns `valid`, `total_events`, `head_hash`, `anchor_prev_hash`, `starts_at_genesis` and, when broken, `first_broken_index`, `first_broken_sequence` and `error_detail`.\n5. **Say what was proven**: `valid: true` means the events passed in are consistent with each other from `anchor_prev_hash` on. It proves the chain is complete only when `starts_at_genesis` is true and the caller compares `head_hash` with a value kept elsewhere.\n\n## Supporting References\n\n- See [Verification Guide](references/verification.md).\n"
}

SHA-256 of public snapshot: 16331344e0edd2e47b526abbbebd06759eb59dd5bed304771c47d1856dc804f7