mirror of
https://github.com/profullstack/logicsrc.git
synced 2026-10-05 06:05:28 +00:00
Anthony Ettinger
1d69dc3804
* 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>
31 lines
2.4 KiB
TypeScript
31 lines
2.4 KiB
TypeScript
// The facts the /openerrand landing page shows, kept apart from page.tsx so
|
|
// contract/openerrand.contract.test.ts can hold them against docs/openerrand.md.
|
|
|
|
/** The step kinds, in the order the spec's Steps table lists them. */
|
|
export const STEPS: Array<[string, string]> = [
|
|
["page", "A form page: fill it from the rules, then press its forward button."],
|
|
["wait", "An interstitial the page clears by itself, such as a proof-of-work bot check. Waited out, never solved or bypassed."],
|
|
["declare", "A legal attestation. Ticked only on the principal's consent for this run, given after seeing the values."],
|
|
["identity-proofing", "A selfie, a video call or an ID scan at a provider such as ID.me. Never driven by the runner: the person does it in a visible window."],
|
|
["code", "A one-time code by text, email, call or app, relayed by the person through a terminal, a file or the runner's own page."],
|
|
["mail", "A letter with a PIN. The run ends as waiting and a hand-off card says what to do when it comes."],
|
|
["captcha", "Shown to the principal, or the run stops. A solver only where the errand says so, never on a government, tax, financial, healthcare or identity-provider site, never with a declaration, identity proofing or a secret input."]
|
|
];
|
|
|
|
/** The sensitivity classes, in the order the spec lists them. */
|
|
export const SENSITIVITY: Array<[string, string]> = [
|
|
["public", "Logs, the terminal, hand-off cards, the run record."],
|
|
["personal", "The principal's terminal, the site's own fields, the vault. Never a log, never a card."],
|
|
["secret", "The site's own field and the vault, and nowhere else. Masked as •••• everywhere."]
|
|
];
|
|
|
|
/** Where an input may come from, in the order the spec lists them. */
|
|
export const SOURCES: Array<[string, string]> = [
|
|
["document", "Extracted on the principal's machine from their own files, with the file and page recorded. The document never leaves the machine."],
|
|
["vault", "A key in the principal's vault, read before anything is generated, so a second run reuses the first run's login."],
|
|
["prompt", "Asked of a person at run time. A secret prompt does not echo."],
|
|
["generate", "A fresh random value, written to the vault on success."],
|
|
["derive", "Another input, transformed: the digits of a street address."],
|
|
["candidate", "A part of the chosen shared-secret candidate, such as the tax year the figure came from."],
|
|
["literal", "A fixed value."]
|
|
];
|