# Thinking Space — first hackathon draft

7 October 2026 · Working file format 0.1 · AkashicOMNI v0.5.0 manual method

Open https://akashicnet.org/lifestyle-tools?mode=research#thinking-space

## Save and resume

Write in the open tab, then choose **Save workspace (.json)**. Keep the downloaded file. Resume by opening that JSON and confirming replacement of the current tab's draft. Save the current draft first if you want both. Notes are not uploaded or automatically saved; changing views preserves them only while the tab remains open. A download starting cannot confirm that your device saved the file.

The readable Markdown summary is for reading and sharing. It is not a complete backup. The JSON workspace contains the current record, earlier draft snapshots, optional fields, unrecognised extension fields and attached originals. Each changed save adds a snapshot; an unchanged save does not add a duplicate. History is author-controlled, not authenticated or tamper-evident.

Limits: 2 MB per file, 100 sources, 100 saved snapshots, 10 original attachments and 20,000 characters per ordinary text field. Keep previous files. If you reach a limit, begin a new linked record and cite the previous record ID.

## What transfers

| Record | Handling | What remains to review |
|---|---|---|
| Thinking Space workspace `akashicomni.workspace/0.1` | Structural validation, then full import. Extension fields are preserved. | Meaning, accuracy, sources and self-reported review history. |
| Thinking Space package `akashicomni.transfer/0.1` | Full workspace plus a reduced PRISM Inquiry Module and mapping notes. Re-import requires the package to match the declared mapping; edited or unknown mapping fields stop import. | The reduced module is not a complete record or live synchronisation. |
| Bounded claim-review pilot `format_version: 0.5.0-draft.1` | Recognised input is attached as unchanged raw JSON to a new blank workspace. It is not translated or authenticated. | Every semantic mapping and any attestation. The closed pilot schema is unchanged. |
| Standalone PRISM Inquiry Module `schema_version: 0.1` | Recognised input is attached as unchanged raw JSON, without schema certification or translation. | All fields, provenance and interpretation. |
| Unknown or malformed format | Rejected; the current draft remains. | Keep the file for a reviewed mapping. |

## Narrow PRISM projection

Target: `schemas/akashic-prism-inquiry-module-v0.1.schema.json` in the AkashicNET repository, pinned to commit `570aee1632fc036d8f114c0fa584ad6c198575a2`:
https://github.com/tws9stmcbf-web/AkashicNET/blob/570aee1632fc036d8f114c0fa584ad6c198575a2/schemas/akashic-prism-inquiry-module-v0.1.schema.json

This is a draft interface from separate development work. Compatibility is with this snapshot, not a promise of compatibility with every later PRISM version.

| Workspace data | Module field |
|---|---|
| Question and workspace ID | Name, module ID and claim ID |
| Working term, definition and origin | One definition, conservatively marked contested |
| Exact claim, author classifications, predictions, alternatives, revision condition and uncertainty | One draft claim |
| Source IDs | Associated claim source IDs; source records remain in the workspace |
| Perspectives marked useful, with reasons | Compatible framework names; all dispositions, reasons and source references remain in the workspace |
| Source access, dependencies, rights/context, contrary evidence, optional modules, component mappings, synthesis, disagreements, history and originals | Preserved in the accompanying workspace, not translated into equivalent module fields |

Projection requires the stated mapping fields; an incomplete workspace can always be saved without a projection. A full reading additionally needs a reason and disposition for all twelve perspectives. The interface never upgrades evidence to `established_evidence`, certifies a reviewer, infers subjective experience or approves publication. The module stays `draft`, with publication on `hold` and review requirements retained.

No PRISM database import, graph write, schema-wide adapter or bidirectional database synchronisation is implemented. A standalone edited module cannot overwrite the fuller record. Complete interoperability and independent semantic review remain hackathon work.

## Demonstrate at the hackathon

1. Choose one public abstract or an explicitly fictional example.
2. Record one question, inspected passage, access limit and alternative explanation.
3. Switch between the concise and research views without losing information.
4. Save JSON, open it in a fresh tab and compare the source IDs, notes and snapshots.
5. If the mapping fields are complete, inspect the transfer package together. Identify what the module alone cannot express.
6. Record one misunderstanding, one missing capability and one useful next change.

This is a first working draft for discussion and improvement. Software checks do not establish research validity or benefit for neurodivergent users.