AQ-INST-BRIEF-001 — Institutional briefing: structure and inspection set
1. PURPOSE AND AUDIENCE
This document defines the structure of an institutional briefing on Akasha-Q — a briefing given to a university group, a research institute, a standards or metrology body, or a technical review panel. Its audience can read a method and will ask for the assumption behind a number. It is therefore longer, slower and more falsifiable than the executive briefing (AQ-CEO-BRIEF-001), and it ends not in a decision but in the release of an inspection set.
The institutional case for Akasha-Q rests on exactly two things: the research value of the questions being asked, and the governance quality of how answers will be admitted as evidence. No third argument is permitted.
Nothing has been built. No Akasha-Q element has reached Lab validation. Sections 4 through 8 describe an intended design and a defined process; they contain no achieved results, and the briefing is defective if any sentence implies otherwise.
2. THE TEN SECTIONS
| § | Section | Min | Primary artefact placed on the table | What it may not contain |
|---|---|---|---|---|
| S1 | Programme identity and scope boundary | 4 | Scope statement: Akasha-Q is a communications platform — five layers advanced along the six-rung reach ladder (optical bench, metro fibre/free-space, 20–30 km HAPS relay, CubeSat, operational LEO satellite, constellation). Visvambhara is a separate aerospace programme and the first platform designed to carry an Akasha-Q terminal; the two share one restricted-access record. | Any construction in which Akasha-Q is a satellite, a payload, or a subsystem of another programme |
| S2 | Research question and hypothesis set | 6 | The falsifiable statements the programme exists to test, each with the observation that would refute it | Aims that cannot be refuted by any measurement |
| S3 | Evidence position | 5 | Position on the Part 12 ladder (Concept, Theory, Simulation, Lab validation, Field validation, Dynamic platform, Flight/space, Operational demonstration), stated per element, held separate from the reach ladder Concept Theory Lab validation — none | Aggregating elements into a single maturity figure; conflating reach rung with evidence level |
| S4 | Layer architecture | 8 | L0 Physical Reality, L1 Sensing & Entropy Trust, L2 Timing & Temporal Integrity, L3 Identity & Cryptographic Trust, L4 Dynamic Trust State (AQ-TSE-01), L5 Command Authority, L6 Evidence & Provenance Fabric, L7 Network & Orchestration, L8 AI-Assisted Analysis (advisory only), L9 Systems Engineering & Safety Governance | Any path by which an L8 output reaches a physical effect without passing L5 and the hardware gate at TB-4 |
| S5 | Design commitments and their consequences | 6 | DC-1 measurement precedes inference; DC-2 absence is a value; DC-3 abstention is permitted; DC-4 degradation is monotonic without validation; DC-5 every consequential transition is reconstructable from the Evidence Fabric alone — each with the test that would show it violated | Stating a commitment without naming what would count as breaching it |
| S6 | Trust state and command authority | 8 | States NORMAL, RESTRICTED, CRITICAL, DENY, RECOVERING; outcomes execute, execute-restricted, safe-hold, abstain, deny; the four questions Q1 who sent it, Q2 cryptographically valid, Q3 authorised now, Q4 should it execute under the current trust state, with Q1–Q3 as hard constraints and Q4 able only to reduce what they allowed; boundaries TB-1 physical/system, TB-2 deterministic acquisition (FPGA), TB-3 trust reasoning, TB-4 decision/physical effect (hardware-gated), TB-5 runtime/evidence | Any mechanism by which trust rises other than through the full recovery sequence |
| S7 | Assumptions, conflicts and decision boundaries | 6 | The assumption register; conflicts CF-1..CF-7 with the resolution rule for each; decision boundaries B-1..B-5 with what lies on either side | Presenting an unresolved conflict as resolved, or omitting a boundary because it is uncomfortable |
| S8 | Failure modes and safety governance | 6 | F-1..F-14 with detection surface and the outcome each drives; L9 governance of hazard analysis, change control and stop authority | A failure mode without a detection surface, or one whose default on missing input is benign |
| S9 | Governance record | 5 | Correction record, failure record, independent review record including retained dissents, and the replay mechanism that satisfies DC-5 | A review record from which dissents have been removed or summarised away |
| S10 | Collaboration modes and funding position | 6 | EduRankAI revenue and disciplined reinvestment; the modes of collaboration available and, for each, the rung or metric it would reach sooner; then release of the inspection set | Any statement that a collaboration, grant or capital event is required for the programme to continue |
3. THE PRE-COLLABORATION INSPECTION SET
No institution is asked to commit on the strength of a briefing. Before any collaboration is discussed in substance, six items are released under the restricted-access record. They exist so that a counterpart’s own reviewers can attempt to find the programme wrong.
| Item | Artefact released | What the counterpart is checking | Condition that must halt release |
|---|---|---|---|
| I-1 | Assumption register | That every claim rests on a named assumption, and that assumptions are dated, owned and revisable | An assumption in use that is not in the register |
| I-2 | Risk register | That risks carry owners, detection surfaces and the state transition each would drive | A risk whose mitigation is “monitor” with no observation defined |
| I-3 | Complete node dossier set, including sections 13 and 14 — the unresolved-question and known-weakness sections | That the dossiers are complete rather than curated; sections 13–14 are the test of that | Any dossier supplied with 13 or 14 abridged, deferred or withheld. Partial dossiers are not released at all. |
| I-4 | Correction record, paired with the failure record | That each correction traces to the originating failure entry, and that corrections were made when the evidence arrived rather than when it was convenient | A correction with no failure entry behind it, or a failure entry closed without a correction or an explicit “no change, and why” |
| I-5 | Independent review record, with dissents retained verbatim | That review was adversarial and that minority findings survived into the record | A review round in which no dissent, question or objection is recorded at all |
| I-6 | Replay access to the Evidence Fabric | That a consequential transition can be reconstructed from the Fabric alone, without narration from the programme — DC-5 tested rather than asserted | A transition that cannot be reconstructed without a person explaining it |
The inspection set is released as a whole. An item that cannot be released is not substituted or summarised: the collaboration decision is deferred, the reason is written into the correction record, and the counterpart is told which item is missing and what would complete it.
Figure 1 — From briefing to a counterpart’s own finding
Institutional counterpart
|
v
[ S1 .. S10 briefing ] no commitment requested at this stage
|
v
Inspection set I-1 .. I-6 released as a whole, under the
restricted-access record shared with Visvambhara
|
+---- any item absent or abridged --> DEFERRED, not denied
| reason -> correction record
v
Counterpart's reviewers reconstruct a transition by replay (I-6)
and test DC-1 .. DC-5 against I-1, I-3, I-4
|
v
Written finding, dissents retained --> entered into the review
record (I-5) whether it supports the programme or not
4. HARD CONSTRAINT ON FRAMING
The institutional case is made on research value and governance quality alone. No section, answer, annex or handout may contain geopolitical, sovereign-capability, national-security or defence framing — including when a counterpart introduces it first, invites it, or offers it as the obvious reason the work matters. An invitation to that frame is declined in one sentence, the research question is restated, and the briefing continues from the section it was in. The invitation and the decline are both written into the delivery note.
The same constraint bars the claims: unhackable, impossible to intercept, universally quantum-secure, information-theoretically secure at system level, satellite-ready, space-proven, operational. The words secure, resilient, autonomous, high-precision and low-latency are never used as bare descriptors; each is replaced by the measured quantity with its assumption set and evidence level, or by an explicit statement that the metric is undefined. Where a performance target would go, the metric is named together with the procedure that will later establish its target from measurement.
5. FUNDING POSITION AS STATED IN SECTION 10
Akasha-Q is funded by EduRankAI revenue and disciplined reinvestment. External capital, institutional partnership and government collaboration are treated as accelerants: each is described by the reach rung it would bring forward, the metric it would allow an independent party to measure rather than the programme itself, or the layer it would staff sooner. None is a precondition, a gate or a dependency, and no section of this briefing may be delivered in a way that implies the work pauses without it.
What the programme asks of an institution is therefore narrow and specific: read the inspection set, attempt to refute the design, and let the finding — supportive or not, unanimous or dissenting — be entered into the review record where the next reviewer will see it.