This document is the reverse-engineered specification of Prototype-v7.html. It describes what the prototype does in structured, governed terms — independent of the HTML implementation. This becomes the baseline specification that Andrew will manage going forward.

This is the specification for the v7 prototype of the Participant Statement Toolkit, captured at the point where Andrew's prototype had been iterated to a stable, testable state. It documents the functional architecture and design decisions embedded in the v7 implementation. The specification serves as the baseline for formalizing the toolkit's design patterns.

This document represents a point-in-time analysis. Subsequent decisions or implementation changes may supersede specific recommendations or assessments contained herein.

Type: Dropping — Phase 1 Output
Prepared by: Sub-agent Manager
Source: History/Prototype-v7.html (reverse-engineered)
Status: Awaiting Brian review

This document is the reverse-engineered specification of Prototype-v7.html. It describes what the prototype does in structured, governed terms — independent of the HTML implementation. This becomes the baseline specification that Andrew will manage going forward.

The document has four major structural layers:

Design note: Impairment types appear as pill-shaped toggles (chip UI), not a traditional checkbox list. Selected impairments are visually highlighted. Multiple selections are permitted.

Title: "How This Document Works — The Submission → Response Chain"

A visual flow diagram showing that the Participant Statement is an input to the NDIA, not an output. The NDIA responds with the Statement of Participant Supports.

"We Submit" side (Part A):

NDIA Responds with:

"The Critical Chain" diagram:
Goal → Context → NDIA → Category (01–21) → Funding Type (1–3) → Outcome Domain (1–8)

An expandable reference block explaining how PACE item codes are structured:

CC_NNN_RRRR_P_F

Also includes visual legends for:

Special note included: Explains why Support Coordination (Category 07) maps to Outcome Domain 8 (Choice and Control) but Psychosocial Recovery Coaching (also Category 07, item 07_101) maps to Outcome Domain 6 (Social and Community Participation). Also notes the Registration Group 0132 distinction for Specialist Support Coordination.

Legislative reference: s33(2)(b) and s34(1)(e)–(f)

Guidance callout (non-printed): The NDIA uses this section to determine whether a support should be funded by NDIS or by informal/mainstream systems. Clarity about the boundaries and limitations of existing non-NDIS supports strengthens the case for NDIS funding.

Risk callout (non-printed, between 1.4 and 1.5): "Risks documented here directly justify the Funding Period intervals, Digital Lock requests, and budget architecture recommendations in Part B."

All Block 1 fields are free-text, multi-line, browser-editable (contenteditable divs with placeholder text).

Legislative reference: s33(2)(a)

Guidance callout (non-printed): Under s34(1)(a), the NDIA cannot fund a support unless it assists the participant to pursue the goals in this statement. If a goal is not here, it cannot be funded.

The prototype ships with 4 default goal cards. Additional cards can be added dynamically (no stated upper limit). Cards can be removed individually.

Each goal card contains:

Sub-section 1: Participant's Goal

Sub-section 2: Goal → Outcome Bridge

Domains listed:

Dynamic behaviour:

Purpose: For each submitted goal, maps the coordinator's anticipated NDIA response — which Support Category, Funding Type, and Outcome Domain should result.

Explanatory callout (non-printed): Justifies why this section is included in the Participant Statement — Section 33(2) permits "other matters" the participant considers relevant.

Reference legends included:

Headers:

Row grouping by Funding Type:

The table is pre-grouped into three funding type sections:

The Funding Type column for each row displays a fixed badge (1–Core, 2–Capital, 3–CB) rather than an editable cell.

Dynamic behaviour:

Legislative reference: Funding Periods · Digital Locks · Flex/Stated

Explanatory callout (non-printed): These are recommendations to the NDIA — not instructions. The NDIA makes the final determination. Budget controls operate at three levels: Flexible vs. Stated categories, Digital Locks on specific items, and Funding Periods.

Table headers:

Row grouping (same as Alignment Matrix):

Dynamic behaviour: "Core Row," "Capital Row," "CB Row" buttons add rows within each section.

Fixed text: "I confirm that this Participant Statement of Goals and Aspirations has been prepared with my input and represents my views, goals, and current circumstances. I understand that Part A of this document will be submitted to the NDIA as the primary input for my Statement of Participant Supports, and that Part B contains my coordinator's recommendations for how the resulting plan should be structured. The NDIA makes the final determination on all funded supports."

Signature fields:

Andrew has indicated there are additional changes he wants to make. These have not been documented in the history files. They will be captured when Andrew's notebook is operational and Andrew can specify them using the governed requirements process.

End of Prototype Specification — v7