# AkashicFLOWBox v0.1.0

18 November 2026 · Public map release

AkashicFLOWBox is the overarching toolbox and connection map. AkashicFLOW is the workflow inside it. The FLOW v0.2.0 working specification accompanies this map; candidate component versions are not public prompt releases.

## Version Manifest

- **AkashicFLOWBox**: v0.1.0
- **AkashicFLOW**: v0.2.0 working specification
- **AkashicMESSAGE**: v0.3.0 current / v0.4.0 candidate
- **AkashicINQUIRY**: v0.2.0 current / v0.3.0 candidate
- **AkashicASSESS**: v0.2.0 current / v0.3.0 candidate
- **AkashicENHANCE**: v0.1.0 current / v0.2.0 candidate
- **AkashicSPIRIT**: v0.2.0 practice draft / v0.3.0 candidate
- **AkashicABSTRACT**: v0.1.0
- **AkashicOMNI**: v0.5.0

## Component Upgrade Contracts

- MESSAGE v0.4.0 candidate: claim IDs and independently recorded evidence, care, agency and wording ratings.
- INQUIRY v0.3.0 candidate: claim-specific denominators, alternative explanations and a discriminating result that changes the conclusion.
- ASSESS v0.3.0 candidate: chosen action, prerequisites, reversibility, reason and conditions for reopening.
- ENHANCE v0.2.0 candidate: problem, applied change, affected claim IDs, check type, outcome and unresolved gaps.
- SPIRIT v0.3.0 candidate: named lens, attributed symbolism or tradition, alternative reading, consent and a freely chosen act of care; evidence ratings remain separately grounded.

## Regression Review

Use the existing AkashicTEST001 blind-review protocol. Compare identical cases under matched model settings and source access, mask versions, randomise output order and use two independent reviewers. Record errors caught, unsupported claims introduced, useful edits, reviewer disagreement and effort. QMM and AkashicINQUIRY012 are retrospective worked examples only. Independent evaluation is pending.

## Release Completion

Record exact version, audience, verified destination, check types and unresolved gaps. A wording pass does not establish source accuracy, rendering quality or reader outcomes. Manual hand-offs are not automatic integrations.

## Directory

### Communication & Relationships

- Constructive Debate — Working framework — /lifestyle-tools#catalogue
- The Unhurried Reply — Published practice — /the-unhurried-reply
- RELATE — Proposed branch — /possible-futures#proposed-branches
- Mettā-Awareness — Reflection practice — /metta-awareness

### Reflection & Everyday Practice

- Thinking Space — Interactive worksheet — /lifestyle-tools#thinking-space
- 19-Lens Living Spectrum — Reflection map — /intelligence-spectrum
- Wisdom Matrix — Reflection tool — /walking-with-wisdom#matrix
- Wisdom Compass — Reflection tool — /walking-with-wisdom#compass
- Daily MEDS — N2N habit framework — /lifestyle-tools#catalogue
- Interchangeable Pyramids — Reflection tool — /synchronicity#pyramids-title
- Embody the Dharma — Contemplative companion — /embody-the-dharma

### Experience & Meaning

- AkashicNEURO · 3D Doings — Mind–Body–Heart–Spirit companion — /akashicneuro
- AkashicSPIRIT — Practice draft v0.2.0 — /lifestyle-tools#akashicspirit
- Synchronicity Reflection — Reflection prompts — /synchronicity
- Unity of Wisdom — Spiritual context — /unity-of-wisdom

### Research & Evidence

- Paper Reader — Study notes and locators — /akashic-inquiry/paper-reader
- Mettā EXPAND² — Discern · Deepen · Synthesis — /lifestyle-tools#akashicinquiry
- PRISM Inquiry Module — Draft transfer format — /akashicomni/research-kit#working-draft
- AkashicTRACE — Research companion — /akashictrace
- N2N Noetic Operating System — Experience-to-question practice — /noetic-sciences#toolkit-origin
- From “Psi” to Precision — N2N overview — /community/archive?q=1syzly9#archive-results
- Consciousness Evidence Trail — Worked examples — /akashicomni/consciousness-evidence-trail
- AkashicOMNI — v0.5.0 · Twelve perspectives — /akashicomni/v0-5-0

### Synthesis & Publication

- AkashicABSTRACT — v0.1.0 · Summary and claim table — /lifestyle-tools#akashicabstract
- AkashicJOURNAL — Publication destination — /magazine#akashicjournal
- AkashicTEST — Case studies and review protocols — /akashictest

### Connected Workspaces & Experiments

- AkashicENGINE — Editorial workspace · manual records — https://akashicnet-inquiry-workspace.vocal-crow-3599.chatgpt.site
- Corpus Rotation / Evidence Intake — Private evidence-intake workspace — https://corpus-rotation-evidence-intake.vocal-crow-3599.chatgpt.site
- AkashicDIAGNOSIS — Prototype · v0.1.0 — /akashicdiagnosis
- AkashicONE · PYRAMID — Private puzzle experiment — https://akashicone-pyramid.vocal-crow-3599.chatgpt.site

## Implemented Prompt Editions

Independent comparative validation is pending. These version increments describe implemented editorial contracts and are not claims of measured reliability.

### AkashicMESSAGE v0.4.0-beta.1

Review the supplied wording. Record scope, audience, source locators, sample size and missing context. Give each distinct claim a stable ID. Preserve exact excerpts and distinguish observation, testimony, research finding, inference, speculation, value judgement and request. Rate evidence, care, agency and wording separately with a reason and source for each judgement. Stakes are separate from tone. Include the strongest plausible alternative reading, counterexamples and context that could change the judgement. Use relevant lenses only; distinguish not applicable from insufficient evidence. Carry claim IDs and uncertainties forward. Do not infer motives, individual biology or intelligence from wording. Return a claim register and a proportionate next step.

### AkashicINQUIRY v0.3.0-beta.1

Use Mettā EXPAND²: Discern, Deepen, then synthesis. Preserve the case scope, claim IDs, source locators and framework versions. For every material claim record what each source measured, design, population, date, denominator, uncertainty and applicability. Distinguish observed findings from synthetic, modelled or proposed results. Keep accuracy, first-report timing, information access and causal or metaphysical explanations as distinct claims when relevant. Compare the strongest plausible alternatives. State a result or observation that would discriminate between explanations, what a precise null would mean and what leaves the question inconclusive. Missing evidence remains missing. Return Question, Current Answer, Evidence, Limits and What Would Change the Answer, plus the updated claim register.

### AkashicASSESS v0.3.0-beta.1

Use the evidence and claim IDs already recorded. Compare relevant actions including clarification, revision, a boundary, private feedback or pause. For each option record its purpose, evidence, audience, consent where relevant, prerequisites, likely amplification, benefit, trade-off and reversibility. Select an action with a reason, conditions for taking it and conditions for reopening it. Distinguish a suggested action from one actually authorised or completed. Preserve legitimate criticism and invited advice. Return an option table and a decision record linked to the affected claims.

### AkashicENHANCE v0.2.0-beta.1

Apply the chosen changes within the authorised scope. For every change record the original problem and source finding, before and after, rationale, affected claim IDs and implementation state. Recheck the claims, links or behaviour affected by the edit. For every check specify type: wording, source verification, calculation, rendering or reader reception; record method, result and remaining uncertainty. A wording pass does not imply accuracy, browser success or reader benefit. Carry unresolved issues forward. Stop when required checks pass and no unresolved issue blocks the intended delivery. Reopen for new evidence or failed checks. Return a before-and-after table and a release receipt with exact version, destination, actual audience, verification time and follow-up gaps.

### AkashicSPIRIT v0.3.0-draft.1

Begin from the requested spiritual or esoteric perspective. Record the person’s own words and chosen boundaries. Name the reading as symbolic, tradition-based or metaphysical inquiry. Attribute interpretations and cite the named teaching in its cultural setting where available. Explore at least one plausible alternative reading without requiring belief or disclosure. Separate personal meaning and testimony from factual, biological and causal claims; route checkable claims to AkashicINQUIRY without changing evidence ratings to fit the lens. Respect community access and reuse protocols. Record which lenses are relevant, not applicable or insufficiently evidenced. Offer one small act of care that people can freely decline and one question to leave open. If revising copy, use AkashicENHANCE and recheck affected claims. Reader or practice outcomes remain untested unless observed and recorded.

## Changelog · 18 November 2026

- Added routing and a shared record contract.
- Added stable claim IDs and explicit evidence categories.
- Added claim-specific alternatives, denominators and discriminating outcomes.
- Added decision prerequisites and reopening conditions.
- Added typed rechecks and release receipts.
- Added spiritual reading attribution, relevance and a freely chosen act of care.
- Preserved legacy editions; no independent validation claim.


## After Every NEXUS or STATE Run

After every AkashicNEXUS or AkashicSTATE run, including reruns, finish with a Post-Run Human Review handoff. Invite Jatinder Sahota to review as Creator / Owner-Reviewer. This is a separate human review; creator involvement means it is not independent external validation. Offer an answer-free packet where suitable and record whether answers were actually hidden, seen or unknown. Record the run ID and edition, scope, reviewer role, method, date, judgements, disagreements and reasons, corrections and rechecks. Keep Owner Review and Independent External Validation as separate statuses; use Pending until actual evidence supports another status. Preserve dated before-and-after records in AkashicLEDGER or the current versioned record. Owner review may support a justified AkashicSTATE reassessment but never raises ratings automatically. Respect the authorised audience, private source metadata and existing HOLD boundaries. This adds a required handoff, not a new publication permission gate.

See `package/post-run-review-protocol.json`.
