1 November 2026 · Working Version 1.6
The original independent review remains historical evidence. This addendum records subsequent software and specification work. Client, expert and operational acceptance are separate and remain pending.
Publication: Version 1.6 is published on the prototype site. The original 172 release files were read back and matched the checked package. Publication receipt. Management downloads include architecture extension A1; its publication has a separate receipt. All 15 client and expert decisions remain pending in Institution review.
| Item | Implementation | Verification | Institution decision |
|---|---|---|---|
| IR-001Public source eligibility | Fixed and verified in prototype | 125 targeted checks; 48 independent checks; all 11 regressions passed | Pending |
| IR-002PMU scope | Specification and proposal labels updated; institutional decision pending | 125 targeted checks; 48 independent checks; all 11 regressions passed | Pending |
| IR-003Requirement provenance | Specification updated; institutional decision pending | Document/register structural verification passed; future service acceptance not executed | Pending |
| IR-004Clause acceptance | Specification updated; future acceptance not executed | Document/register structural verification passed; future service acceptance not executed | Pending |
| IR-005Release scope | Specification updated; institutional decision pending | Document/register structural verification passed; future service acceptance not executed | Pending |
| IR-006NFR conditions | Specification updated; service conditions pending | Document/register structural verification passed; future service acceptance not executed | Pending |
| IR-007Delivery scope | Specification updated; institutional decision pending | Document/register structural verification passed; future service acceptance not executed | Pending |
| IR-008Definition and mapping preview | Prototype validation fixed; dictionary approval pending | 125 targeted checks; 48 independent checks; all 11 regressions passed | Pending |
| IR-009Future contracts | Specification updated; provider/operator decisions pending | Document/register structural verification passed; future service acceptance not executed | Pending |
| IR-010Sample meaning | Model fixed and verified; current image synchronization checked separately | 125 targeted checks; 48 independent checks; all 11 regressions passed | Pending |
| IR-011Bounded maintenance | Build and policy ownership consolidated; larger restructuring deferred | 125 targeted checks; 48 independent checks; all 11 regressions passed | Pending |
125 targeted checks and 48 independent negative checks. Fresh regressions passed: 11 of 11. See the downloadable evidence summary for exact commands, fixtures and limitations. Future service cases are not executed by these browser demonstrations.
Current gap register · Requirement matrix · Correction evidence summary
Read management report · Editable report · Editable presentation
Use the existing C01–C12 and E01–E03 decisions in Institution review. Scope, ownership, data rights, definitions, methods, local parameters, inclusive access, operator, hosting, measurable service conditions, final consultancy validation and handover remain pending. No saved prototype action creates approval.
Current public list, detail, map, count and export use one exact source/version/rights rule. Unknown permission or audience is denied; earlier explicitly permitted versions remain available.
Remaining dependency: C04/E01; any institutional exception policy remains pending
Next role: Source custodian and competent reviewer
Requirements: SH-GEO-FEAT-019; FR064; FR095; FR106; FR133; FR134
The disputed panel and five decisions remain proposed, outside evidenced accepted totals. Physical-progress functionality remains available.
Remaining dependency: C01/C02/C10/C11/C12
Next role: PMU and authorized client
Requirements: FR110; FR123; FR150; FR156
All 190 requirements have source class, passage/locator, need, proposed owner, ownership status, release, decisions and validation state. Twenty-five source/need passages link both ways.
Remaining dependency: C01/C02/C04/C11
Next role: Client, institutional stewards and analyst
Requirements: All 190 IDs
The annex contains 470 clauses, 637 cases, seven shared suites and 20 synthetic fixture contracts. The 487 future service and 150 prototype design case plans remain not executed; separate executed correction receipts are not substituted for them.
Remaining dependency: C01/C08 and applicable source/policy decisions
Next role: Acceptance owner and delivery/test team
Requirements: All 190 IDs
One release matrix retains five work packages, seven capability areas and 820 candidate decisions. There are 179 proposed core requirements, including four conditional branches, and 11 whole conditional options. Accepted and formally deferred counts require evidence; all 190 acceptance decisions remain unknown.
Remaining dependency: C01/C02/C12
Next role: Client and PMU
Requirements: All 190 IDs
All 14 NFR profiles retain the existing numerical proposals and define owner, workload, volumes, devices, network, language/accessibility, boundary, window, exclusions, method and pass/fail rules. Unknown accepted values remain pending.
Remaining dependency: C05/C06/C07/C08
Next role: Client, receiving operator and specialists
Requirements: NFR01–NFR14
Responsive low-bandwidth core access remains required. Additional field/offline channels and stronger deployment separation are conditional. Logical interface boundaries do not mandate separate deployments.
Remaining dependency: C01/C06/C07
Next role: Client, field representatives and operator
Requirements: FR139; FR140; FR141; SH-GEO-FEAT-017; FR155
Existing proposals record version, proposed owner, relationships, type/unit/vocabulary, missing meanings, sensitivity, source binding and change rules. Missing, zero, false, empty and not applicable remain distinct. Unknown definition/mapping versions are denied. Demo approval activates no institutional definition.
Remaining dependency: C02/C04/E01
Next role: Appointed stewards and competent domain reviewers
Requirements: FR014–FR021
Future interface documentation retains validation, errors, bounded retry, duplicate protection, version/conflict, permissions and recovery. The real-system bridge is a local future-contract preview; no installed provider interface or physical production schema is claimed.
Remaining dependency: C04/C05/C07/C08/C12
Next role: Provider owners, client and receiving operator
Requirements: FR143–FR148; FR155
The rice sample has mutually exclusive fictional seed categories A–F and 586 eligible plots. Count, share, chart, supporting rows and export agree. Unknown/multiple-category rows are excluded; invalid counts fail and zero denominator is unavailable. Six composition examples received compatible fictional categories.
Remaining dependency: C01/C02/E01; local scientific/source use remains pending
Next role: Client and appointed scientific/statistical expert
Requirements: FR099; FR101; NF001; NF002
Current immutable inputs, source-owned correction modules, data/state/policy owners and resource/build manifests make the retained delivery approach reproducible. No new platform, application or persistence store was introduced. Larger optional restructuring is deferred with a reason.
Remaining dependency: Further maintenance scope under C01; no authority inferred
Next role: Prototype maintainer
Requirements: FR142
Previously downloaded copies cannot be recalled. Browser role and permission previews do not prove server security. Provider compatibility, complete accessibility/language usability, scientific suitability, actual service performance and recovery remain external evidence requirements. The real SHARED application was not connected to or changed.
Extension A1 adds 13 views to the 33 retained routes, twelve capture contracts, source and device catalogues, definition changes, storage choices and synthetic Expert Hub journeys. The SRS, appendix, coverage annex and management downloads are synchronized.
Executed architecture evidence: 66 model checks and 28 independent checks. Institutional acceptance plans remain separate. Start with the lean foundation; analytical and high-volume extensions need measured justification.
Open architecture and examples · Requirement bindings · Extension release status
Start with Overview, follow a Focused view, or open the Complete diagram. The calculation appendix now explains each question and what changes when an input changes. Try the rice and weather example.
Use Institution review for all client and expert decisions.