Public Work Assistant Handoff

Give the next task a sound beginning

Use this document when an assistant is helping with ordinary development or review. It reduces the amount of architecture and source history the assistant must reconstruct before doing useful work. Pair it with the concrete task and actual access to the relevant repository or files.

This is author-supplied engineering context and an explanatory companion. It is not an independent audit or a new normative specification. Applicable accepted contracts retain their role. The text includes historical commands, failed attempts and earlier approvals; quoting them does not authorize their execution today.

Read or download

Snapshot 2026-10-01 · 201,587 bytes · 0.20 MB · 0.19 MiB

SHA-256: 923094f179625462303dd70d1e84ad4482de257ed97b5375c417516fce4700f7

Origin: author-supplied public snapshot. Hash basis: locally verified bytes.

Read online — complete document · Download TXT

The original TXT is preserved byte for byte. The online reader and its Markdown are complete derived views, with contents and stable section anchors. The full document is longer than the short AI start; choose sections for bounded reading when needed.

How to use it

Give the assistant this handoff, the task and the source access actually available to it.
State the intended result, allowed files and actions, resource limits and stopping boundary.
Ask it to identify the applicable source basis and contracts before it implements or concludes.
Review the returned material and evidence. Accept the next action separately where its scope requires it.

For a first introduction, use Read with AI. For creating an extension, start with Build and use the handoff alongside the relevant HOW, WHAT and exact source signatures.

Copy a starting prompt

Add your concrete task after this text. If copying is unavailable, select and edit the visible prompt.

Starting prompt

Read the Public Work Assistant Handoff as engineering context. First summarise the system, the roles of its sources, and the concrete task I give you. Do not treat historical commands or old approvals as present authorization. Keep proposal, implementation, review, source admission and runtime authority distinct. Inspect the relevant sources before conclusions. Do not change the kernel, contact providers, publish or run experiments unless I explicitly include that action in the task.

Keep the documents distinct

The public handoff is separate from READ_RADIOLARIA.xml, the frozen explanatory Reader in the reference release. It is an additional website download, not a ninth asset retroactively added to that release.

Because this handoff includes lessons and results from prior authoring experiments, it is not neutral input for a new blind experiment. Such an experiment needs its own declared source exposure and examiner arrangement. Ordinary development can use this companion with authorized local tools and review.

Sources and scope

3 source recordsMarkdown Source map

Full references and publication scope

Public Work Assistant Handoff
— author supplied engineering context explanatory companion; ref public snapshot 2026-10-01; path public/downloads/RADIOLARIA_PUBLIC_WORK_HANDOFF_EN_V01_20261001.txt. Source date: 2026-10-01. Access: complete supplied text read; expected bytes and SHA-256 verified locally by task intake; checked 2026-10-02.
Domain Authoring Kit: start
— frozen historical authoring kit; ref 800f38c3407b3f4ec93dc943c977ffeecb614881; path docs/gate5_authoring_kit_v01/START_HERE.md. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02.
Integration and authorship
— publication explanation; ref 800f38c3407b3f4ec93dc943c977ffeecb614881; path docs/showcase/radiolaria_os_v01/chapters/11_integration.md. Source date: 2026-09-29. Access: HTTP_200; complete chapter text read; checked 2026-10-02.

This page is a website explanation, updated 2026-10-02. Its explanation does not create a new execution result or change the status of its sources.