bbs.profullstack/logicsrc
1
0
Fork 0
mirror of https://github.com/profullstack/logicsrc.git synced 2026-10-05 06:05:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
logicsrc/packages/schemas/README.md
Anthony Ettinger 1d69dc3804
OpenErrand 0.1: an errand on a website with no API, with the human steps kept human (#227) 
* OpenErrand 0.1: an errand on a website with no API, with the human steps kept human

docs/openerrand.md mints OpenErrand: one JSON file per errand (register an
account, download a transcript) naming the site, the inputs with a
sensitivity class and ordered sources (document, vault, prompt, generate,
derive, candidate, literal), field rules matched by id then label, page and
wait steps, five human gates a runner never performs (declare,
identity-proofing, code, mail, captcha), outcomes, the never-retried shared
secret, vault and download outputs, hand-off cards that may name only public
inputs, the publisher index at /.well-known/openerrand.json, and thirteen
runner rules. The worked example is the MyFTB business registration that
cli-tools `ftb` performs (profullstack/cli-tools#125), with no personal data.

- @logicsrc/schemas: openerrand + openerrand-index schemas and fixtures
- @logicsrc/validators: semantic checks (references, templates, no personal
  or secret input on a card) and tests that validate the spec's own examples
- logicsrc-web: registry entry (process family), /openerrand landing page,
  the example and the index served as static files, contract tests

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

* OpenErrand: hand-off cards stay on the surface that owns the data

Anthony's ruling: tax and finance data never touches a social or promotion
tool, and nothing is sent to a CPA or preparer.

- Hand-off cards are delivered only on the surface that owns the errand's
  data (for a tax or finance errand, the principal's finance app through its
  CLI, PWA, MCP server or API, such as CoinPay, or the runner's terminal),
  never a social, promotion or third-party posting service, and never to
  anyone but the principal. A card for an errand with personal or secret
  inputs does not leave that surface. Runner rule 9 says the same.
- The run record and the sample run name the card by an opaque id
  (pin-letter/7f3k2q) instead of a mynaposter.com URL; the myna mention is gone.
- `principal: represented` no longer cites a preparer with a power of attorney.
- The FTB card's last step no longer suggests sending the PIN to someone else.

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

* OpenErrand: user-agent rule, captcha solver policy, reference runner note

Anthony's answers on #227 ("go with your recommendations"):

- Rule 11: a runner may run headless with a normal desktop browser user agent
  (dropping HeadlessChrome) and nothing more: no fingerprint spoofing beyond
  the UA string, no stealth plugins, no solving or evading a bot challenge.
  A challenge the browser completes itself is a wait step; any other is a
  captcha gate.
- Captcha solvers: new site.sector and captcha step `solver`
  (forbidden by default | allowed). Never allowed on government, tax,
  financial, healthcare or identity-provider sites, nor on any errand with a
  declare or identity-proofing step or a secret input; elsewhere only when the
  file says so, with every use logged. The validator rejects `allowed` in the
  forbidden set or without a stated sector; six new tests. The FTB example
  states sector "tax".
- Reference runner: @logicsrc/openerrand / `logicsrc errand run`, marked in
  progress; ftb stays the runner the example was taken from.
- Name stays OpenErrand; family stays Agents and process.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-04 08:57:10 -07:00

1.9 KiB
Raw Blame History

@logicsrc/schemas

Canonical JSON Schemas (draft 2020-12) for the LogicSRC open coordination standards, maintained by Profullstack, Inc.

Schema families include:

  • LogicSRC core — logicsrc-*.schema.json: tasks, agents, runs, events, plugins, connected accounts, email messages, social posts.
  • AgentAd — agentad-*.schema.json: a disclosed, agent-readable advertising contract for CLI tools and AI agents (ads, placements, requests, responses, impressions, clicks, campaigns). See docs/agentad.md in the repo; cl1s.tech is the reference network.
  • OpenWall draft — openwall-message and openwall-receipt exports define sender-side audience jobs and private delivery events. Fixtures are in fixtures/openwall. See docs/openwall.md for consent, routing, and runtime requirements beyond structural validation; no OpenWall delivery runtime ships.
  • OpenRental draft — the openrental export describes listings of OpenAgent profiles and OpenSwarm file-key references, with metadata and CoinPay rental offers. @logicsrc/validators also checks membership and rental references.
  • OpenErrand - the openerrand and openerrand-index exports describe an errand a runner performs on a website with no API, and a publisher's list of them. Fixtures are in fixtures/openerrand. @logicsrc/validators also checks references, templates, and that no hand-off card names a personal or secret input. See docs/openerrand.md.

Install

npm install @logicsrc/schemas

Use

import adSchema from "@logicsrc/schemas/agentad-ad" with { type: "json" };
import taskSchema from "@logicsrc/schemas/task" with { type: "json" };

Schema $ids resolve under https://schemas.logicsrc.com/. Validate with any draft 2020-12 validator (e.g. ajv/dist/2020.js), or use @logicsrc/validators from the monorepo.

License

MIT © Profullstack, Inc.