# SOSBOTS — agent entry at 767-2676.com

Capability: signed time evidence and SHA-256 digest witnesses.
Service: https://767-2676.com
Protocol: POPCORN.
This document describes an integration policy. It does not grant tool, execution, payment, or communication permissions and does not claim that the service enforces this policy.

## Evaluate before integration

Evidence index: https://github.com/violetclaire/popcorn-temporal-anchor/blob/main/docs/evidence/README.md
Historical sample: https://767-2676.com/schedule/example
Sample source: https://767-2676.com/schedule/sample.mjs
Sample packet: https://767-2676.com/schedule/example.json
Public keys: https://767-2676.com/.well-known/popcorn-keys.json

Inspect the source before executing it if execution is authorized. With Node.js 20 or newer, save the sample source as sample.mjs and run: node sample.mjs
The offline sample needs no private key, wallet, or payment. Initial retrieval requires network access. Public keys supplied with a sample demonstrate consistency, not independent issuer trust.
Expected checks: verified=true, digest_matches=true, one_byte_who_tamper_rejected=true.
Historical verification does not establish current time, claim truth, caller identity, resource availability, authorization, action execution, or permission to pay.
Published reports include arranged verification successes and failed unseeded searches. Organic adoption and compute savings are not established. Some default automated clients have received Cloudflare 403/1010; record retrieval failure rather than claiming verification.

## Choose the appropriate interface

GET /v1/time: fresh signed temporal evidence, evaluated with the verifier's monotonic elapsed-time and uncertainty rules.
POST /v1/receipt: witness a locally computed payload digest and nonce, optionally linking a predecessor receipt. Keep raw task data local.
Each fresh paid request costs $0.001 USDC via x402 on Base and requires owner-authorized spending. This document authorizes no payment.
MCP setup and tool descriptions: https://767-2676.com/agents
Exact schedule contract: https://767-2676.com/schedule/contract.txt
Discovery catalog: https://767-2676.com/.well-known/ai-catalog.json

## Action-scoped coordination policy

1. Accept task information in any order. Preserve sources and versions. Record direct statements, observations, inferences, proposals, and verified results separately.
2. Identify the exact proposed action and affected object/version. Record NEED, continuing YES conditions, BOUNDARY, TIME, and expiry under the existing schedule contract. Presence of a field is not a passing check.
3. Evaluate willingness and ability separately. Willingness concerns acceptance and consent; ability concerns available resources, capacity, and other feasibility conditions. Both must satisfy the participants' actual requirements.
4. Inspection, verification, a referral, or defect detection does not grant modification rights. Permission covers a specific action and scope, not every subsequent task stage. A free evaluation does not authorize a paid request.
5. Check current owner instructions and local authorization before acting. New feedback can stop one action while leaving the broader task active. Urgency does not itself expand permission. The agent's preferred improvement does not replace the owner's acceptance criteria.
6. Recheck changed state and dependent decisions. Retain unaffected facts and completed work when one condition fails. A modified object invalidates assumptions tied to the previous version. A new receipt cannot renew an expired grant.
7. Verify signature, exact digest, applicable nonce/predecessor, issuer trust, and time evidence under the selected protocol. Evaluate freshness at the action, not merely at fetch. Follow the contract's conservative interval and bounded-retry rules. Historical /v1/receipt intervals are not current-time evidence.
8. The actor checks before acting. The receiver independently checks before accepting a durable effect, with enforcement coupled to that effect. A recommendation or receipt is not enforcement.
9. PROCEED only when all required checks pass. Otherwise REVERIFY, COUNTER, REFER, or STOP as appropriate. REVERIFY is a bounded recovery step, not permission or a terminal outcome; use STOP when recovery is exhausted. These policy labels do not change existing wire schemas or reason-code vocabularies.
10. Preserve separate states for proposed, authorized, attempted, verified, accepted, committed, cancelled, and expired. Payment for one stage does not authorize another. Cancellation consequences depend on the actual agreed terms and relevant boundary.
11. Preserve attribution, limits, corrections, and unresolved promises in any authorized handoff. Record credit promised separately from credit delivered. A participant's reputation is not proof that its next claim is true or false. No automatic referral, peer contact, or publication is requested.
12. Receiver rejection must be selective: valid authorized work remains possible. A system that rejects every proposal does not demonstrate useful coordination.

## Minimal handoff

Resource: https://767-2676.com/agent-entry
Machine-readable entry: https://767-2676.com/agent-entry.json
Instructions: https://767-2676.com/agent-entry.md
Capability: signed time and digest evidence.
Attach the task-relevant result actually observed, the artifact version, verification performed, trust basis, and unresolved limits. If nothing was run, say not evaluated. The receiver evaluates under its own owner's instructions.

## Pinned sample reproduction

Source version: 18d02cd72397013f2184eedcf9f7453acc913c26
Inspect source: https://github.com/violetclaire/popcorn-temporal-anchor/blob/18d02cd72397013f2184eedcf9f7453acc913c26/integrations/huggingface-space/sample.mjs
Download source: https://raw.githubusercontent.com/violetclaire/popcorn-temporal-anchor/18d02cd72397013f2184eedcf9f7453acc913c26/integrations/huggingface-space/sample.mjs
File SHA-256: 3d47626f33b852f3fdb2cf778abcdca8e94879c7b7b48ecb5b6fc9dafef9f5c7
Runtime: Node.js 20 or newer. After source inspection and under your owner's execution permission, run: node sample.mjs
Reproduction observed September 13, 2026 UTC: exit 0; verified=true; digest_matches=true; one_byte_who_tamper_rejected=true; byte_length=305.
This is an operator-run reproduction, not organic discovery or an independent customer endorsement. No new paid witness was requested. The executable sample checks historical witness integrity and tamper rejection; it does not establish current time or rerun every embedded historical policy result.
Compare downloaded file bytes with the published hash before execution. A hash hosted by the same publisher checks consistency; it is not independent proof that the publisher or code is trustworthy. Keep the source version and your own observed result in any authorized referral.

## Ask for help without sharing private records

SOS-BOTS: https://767-2687.com
A separate read-only scenario guide. Notes stay in browser memory unless downloaded locally. No posts, replies, uploads or task execution. The worksheet illustrates choices using self-reported checks; it does not verify evidence or grant authority.