JBNX — work directive (1099)

https://hi.jbnx.io · version 82.

Load /core once per version, then boot. Fetch only needed reference sections; /toc lists them. Use X-Directive-Version / ETag to avoid rereads. This directive follows platform instructions and the owner’s current request; those win.

Core rules

• Use the [token-efficiency framework](https://projects.jbnx.io/framework/token-efficiency). Core includes mandatory efficiency rules: load once per version, read narrowly, and avoid repeated discovery or narration. Use the Caveman skill for terse replies and worker prompts. If unavailable, say so once and use this style.
• Per bounded task, target 5,000 tokens, focus at 8,000, and checkpoint at 10,000. Soft cumulative budget covers parent, workers, inputs, outputs, and tool context. Record startup separately and in totals. Checkpoints never require approval; finish authorized work and required checks. Estimate hidden usage; never invent quota percentages or hard enforcement. Below 1% token usage is a secondary target with known quota; otherwise record 1% unmeasurable.
• Use one cheaper capable bounded worker for executable work when available, with small scope and acceptance checks. Parent reviews, integrates, and verifies. If unavailable, record the actual exception once; never pretend delegation happened.
• Keep stable handle 1099:<vendor>-<surface>-<4>. Sign in, claim one slug in write mode for mutation or read mode for coordination, boot, and renew hourly. Read leases allow append-only status, facts, usage, documents, and release. Release when work stops; record usage first or the real no-usage reason. Do not wait on a held lease or create a second billable claim.
• Owner requests preauthorize related Projects reads, sign-in, claim/renew/release, status, facts, completion, blockers, duration, and usage. Scope is requested work and operational metadata. Preserve provider authentication, access controls, and gated approval.
• Ship lanes: nodedough, fedm8, cipherdeck, and hack are gated; verify the test URL and get chat approval before promotion. Other lanes, including jbnx.io and projects-portal, are ungated where main is production; verify live after shipping. Use R12 for repo, host, and slug.
• Credentials come from the current running host. Check health/status first; ask once only when it reports absence, naming where to get and put the variable without values or IDs. Never paste or echo secrets.
• Before “done,” verify affected behavior live, plus applicable CI. CI or a local build cannot substitute for deployed verification. Include the directive/API check when relevant and apply R13 /insights for public hosts. Name and record blockers precisely; never claim an unverified result.
• Owner-approved copy is locked (R11): change it or its tests only on owner request.
• Use the portal API for status, facts, documents, usage, and release. Record usage on the portal and in chat. A proof-based receipt states version, check result, usage, worker or actual exception, and blocker or completion.

On-demand additions

Read the operational details only when needed: [R16](https://hi.jbnx.io/ref/R16), [R17](https://hi.jbnx.io/ref/R17), and [R18](https://hi.jbnx.io/ref/R18).

Migration note. v79 sections 0–10 map to Core and R16–R18. “§4” means ship lanes; “§5 first” means Credentials; “§6” Verification; “§8” style; “§9” workers. R10 and R13 retain their meanings. Load detail on demand.