Open the 105-screen walkthrough or find a screen by requirement.
This page keeps the original requirements comparison. For the current SRS and coverage, open SRS documents. Record comments and decisions in Institution review.
The prototype covers the main information journey, but it is not a 100% completed or accepted SHARED system.
Compared the original GCF document, the original system SRS, all 21 detailed chapters, current addenda and the current live prototype. Original requirements were retained.
All 156 chapter requirement IDs and all 49 GCF workflow IDs are present in the prototype register. There are also 20 proposed geographic requirements. The 49 local workflow model checks passed. These counts show traceability and demonstration coverage; they do not show production acceptance.
Demonstrated locally: the relevant local workflow has been exercised. Partial demonstration: a related screen/model exists, with behavior or evidence still to verify. Explained only: a real service, device or operating control is still needed.
Partial demonstration: 78, Explained only: 19, Demonstrated locally: 59. No completion percentage is claimed.
Open. PMU and institution owners must approve the SRS, applicable scope and acceptance evidence. Later review additions do not silently replace the original outcomes.
Source: Original charter; original SRS ACC-001; chapters 19–21
Open. Role selectors demonstrate responsibilities. Prove real sessions, invitations, expiry, delegation, revocation and cross-institution denial through the actual service and target database.
Source: FR001–010; FR136; FR139; FR146
Open. The review prototype uses browser storage. Prove API-backed shared records, genuine quarantine/scanning, download permissions and immutable server audit in the operational system.
Source: FR008; FR032; FR130–131; FR147–149
Open. Local PDF/Word/text matching is usable. OCR, complex tables, configured extraction, multi-destination batch handling and independent mapping-versus-value review still need implementation or separate service evidence.
Source: FR047–050; W19
Open. Many decision views use clearly labeled samples or public context. Obtain the exact dated institution records, required GN/catchment detail, denominators, rights, completeness and owner acceptance.
Source: FR031; FR034; FR075–079; FR101; chapter 21
Open. The 820 examples and 57 calculation families demonstrate proposed rules. Specialists must validate suitability, thresholds, allocation, uncertainty and approved live data bindings before operational use.
Source: FR079; FR085; FR101–107; FR123–125
Open. Public display geometry and bounded analysis work. Verify private SHARED layer/project access with each permitted role, approved original geometry and representative vector/raster volumes. A successful public map does not prove the private connection.
Source: FR026; FR063–074; geographic addendum
Open. Browser walkthroughs are available. Encrypted mobile storage, device GPS accuracy, revocation, offline restart, synchronization and conflict handling need signed-build/device evidence. Desktop-only review does not remove these original delivery requirements.
Source: FR139–141; original FR-MOB-001
Open. Participant, support, market and PES examples exist. Confirm lawful participant access, receiving/appeal policy, actual source records, scheme authority, eligibility, rates and verified-service/payment-stage evidence.
Source: FR082–093; FR134–135
Open. Local report/join, project, task and closure models are demonstrated. Prove full real-source lineage, accepted monitoring plans, approved project revisions, fixed report evidence and closure across the operational service.
Source: FR094–100; FR108–128
Open. Three-language screens and a 15-section guide are available. Institution reviewers must accept practical wording and run each applicable role workflow. A translated screen or a mapped guide item alone is not acceptance.
Source: FR137–138; W18–W19
Open. Keyboard/screen-reader/contrast, approved browser/device tests, target-like load, network failure and authorized security assessment remain acceptance work. Passing scenario checks does not establish these properties.
Source: Chapter 18; original ACC-006–008
Open. The review release has verified file backups and checksums. Coordinated database-plus-protected-file restore, agreed recovery targets, monitoring, ownership, incident support and production go/no-go require operational evidence.
Source: FR151–155; original ACC-009 and ACC-014
Fixed in review correction. The live check incorrectly expects 156 total requirements. Preserve all 156 original and 20 geographic requirements, check unique IDs and required families, and rerun the full 49-workflow/51-check suite.
Source: FR150; FR156
Fixed in review correction. Leaving File upload during a pending read could reopen data entry after the read completed. Discard late results after navigation and keep the selected screen; retain draft data.
Source: FR068; FR137; W19
Corrected in living SRS. The living SRS introduction calls an August 96-row matrix definitive. Preserve that historical evidence and point readers to the dated source comparison and current prototype audit without declaring production acceptance.
Source: FR150; original BR-015
Use the source reference and requirement ID during institution review. The CSV includes the full extracted requirement and source location.
| Requirement | Source | Prototype coverage | Next check |
|---|---|---|---|
| FR001 Maintain organizations and people | Chapter 3 · 3.4REQ-IAM-001 | Partial demonstrationPeople and households; People and appointments; Verified account links | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR002 Manage accounts and roles | Chapter 3 · 3.4REQ-IAM-002 | Partial demonstrationPeople and appointments; Verified account links | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR003 Limit delegated powers | Chapter 3 · 3.4REQ-IAM-003 | Partial demonstrationPeople and appointments | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR004 Use standard secure sign in | Chapter 3 · 3.4REQ-IAM-005 | Explained onlyPeople and appointments | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR005 Use the signed in user identity | Chapter 3 · 3.4REQ-IAM-006 | Explained onlyPeople and appointments | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR006 Invite the intended user | Chapter 3 · 3.4REQ-IAM-007 | Explained onlyPeople and appointments | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR007 Keep the user identity when changing workspace | Chapter 3 · 3.4REQ-ADMIN-WORKSPACE-001 | Partial demonstrationPeople and appointments | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR008 Use one connected platform | Chapter 3 · 3.5REQ-GOV-001 | Demonstrated locallySharing and withdrawal | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR009 Check the full access scope | Chapter 3 · 3.7REQ-IAM-004 | Partial demonstrationSharing and withdrawal | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR010 Let owners control sharing | Chapter 3 · 3.7REQ-STK-ACCESS-001 | Partial demonstrationSharing and withdrawal | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR011 Place all stakeholders correctly | Chapter 3 · 3.1REQ-STK-DOMAIN-NETWORK-004 | Partial demonstrationSharing and withdrawal | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR012 Keep separate owned base domains | Chapter 5 · 5.2REQ-STK-DOMAIN-TREE-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR013 Configure useful workspaces | Chapter 3 · 3.5REQ-PMU-OPS-010 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR014 Maintain versioned domain packs | Chapter 5 · 5.10REQ-DOM-001 | Partial demonstrationDefinitions and vocabulary | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR015 Allow safe configuration only | Chapter 5 · 5.9REQ-DOM-002 | Demonstrated locallyDefinitions and vocabulary | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR016 Keep the original form version | Chapter 5 · 5.10REQ-DOM-003 | Demonstrated locallyDefinitions and vocabulary | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR017 Separate editable settings from software changes | Chapter 5 · 5.9REQ-DOM-004 | Partial demonstrationDefinitions and vocabulary | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR018 Maintain editable vocabularies | Chapter 5 · 5.8REQ-REF-001 | Partial demonstrationDefinitions and vocabulary | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR019 Allow several domain classifications | Chapter 5 · 5.6REQ-REF-002 | Partial demonstrationDefinitions and vocabulary | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR020 Keep business terms in configuration | Chapter 5 · 5.8REQ-REF-003 | Partial demonstrationDefinitions and vocabulary | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR021 Review meanings and impacts | Chapter 5 · 5.9REQ-DOMAIN-SOURCE-001 | Demonstrated locallyCalculation methods; Definitions and vocabulary | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR022 Support several geography schemes | Chapter 5 · 5.7REQ-GEO-001 | Partial demonstrationGeography and boundary history | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR023 Keep place identity and source | Chapter 5 · 5.7REQ-GEO-002 | Partial demonstrationGeography and boundary history | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR024 Link overlapping places | Chapter 5 · 5.7REQ-GEO-003 | Partial demonstrationGeography and boundary history | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR025 Preserve boundary history | Chapter 5 · 5.7REQ-GEO-004 | Partial demonstrationGeography and boundary history | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR026 Validate spatial input | Chapter 5 · 5.7REQ-GEO-005 | Demonstrated locallyGeography and boundary history | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR027 Review boundary changes | Chapter 5 · 5.7REQ-GEO-006 | Partial demonstrationGeography and boundary history | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR028 Search GN divisions within safe limits | Chapter 10 · 10.3REQ-GN-RAIN-001 | Partial demonstrationGeography and boundary history | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR029 Describe each source and dataset | Chapter 6 · 6.1REQ-CAT-001 | Demonstrated locallyShared objects | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR030 Describe versioned fields | Chapter 5 · 5.4REQ-CAT-002 | Demonstrated locallyShared objects | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR031 Define indicators before results | Chapter 11 · 11.8REQ-CAT-003 | Demonstrated locallyMonitoring and indicators; Calculation methods | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR032 Separate original input from curated data | Chapter 8 · 8.1REQ-CAT-004 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR033 Follow up with the provider | Chapter 6 · 6.12REQ-GCF-DP-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR034 Connect usable fields to sources | Chapter 6 · 6.10REQ-LIVE-EVIDENCE-001 | Partial demonstrationShared objects | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR035 Use controlled entry routes | Chapter 6 · 6.3REQ-WF-001 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR036 Follow configured transitions | Chapter 7 · 7.10REQ-WF-002 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR037 Keep submission context | Chapter 6 · 6.3REQ-WF-003 | Demonstrated locallyForm designer | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR038 Keep manual source details | Chapter 6 · 6.3REQ-DATA-INSERT-001 | Partial demonstrationForm designer | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR039 Keep missing values distinct | Chapter 7 · 7.11REQ-DATA-FOUNDATION-001 | Demonstrated locallyForm designer | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR040 Reuse detailed field forms | Chapter 16 · 16.3REQ-SHARED-COMP-002 | Partial demonstrationForm designer | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR041 Validate a batch before confirmation | Chapter 6 · 6.4REQ-IMP-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR042 Approve and save the batch safely | Chapter 6 · 6.4REQ-IMP-002 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR043 Keep the import history | Chapter 6 · 6.4REQ-IMP-003 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR044 Recover repeated upload results safely | Chapter 6 · 6.4REQ-WF-004 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR045 Provide one common file parser | Chapter 6 · 6.4REQ-DATA-FOUNDATION-003 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR046 Register the original purpose | Chapter 6 · 6.5REQ-AI-DOC-005 | Partial demonstrationDocuments and extraction; Extracted suggestions | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR047 Gate real AI processing | Chapter 6 · 6.5REQ-AI-DOC-001; REQ-AI-DOC-003 | Explained onlyDocuments and extraction; Extracted suggestions | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR048 Keep extraction evidence | Chapter 6 · 6.5REQ-AI-DOC-002 | Partial demonstrationDocuments and extraction; Extracted suggestions | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR049 Review several domains from one document | Chapter 6 · 6.5REQ-AI-DOC-004 | Partial demonstrationDocuments and extraction; Extracted suggestions | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR050 Keep mapping approval separate from acceptance | Chapter 7 · 7.7REQ-AI-DOC-004 | Partial demonstrationDocuments and extraction; Extracted suggestions | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR051 Register a controlled source feed | Chapter 6 · 6.6REQ-DATA-FOUNDATION-006 | Partial demonstrationFeeds and devices | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR052 Review provider mappings | Chapter 6 · 6.10REQ-DATA-FOUNDATION-008 | Partial demonstrationFeeds and devices | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR053 Decode supported provider formats | Chapter 17 · 17.4REQ-DATA-FOUNDATION-008 | Partial demonstrationFeeds and devices | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR054 Keep honest row outcomes | Chapter 6 · 6.11REQ-DATA-FOUNDATION-006 | Demonstrated locallyFeeds and devices | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR055 Prevent repeated source events | Chapter 7 · 7.4REQ-DATA-FOUNDATION-006; REQ-GN-RAIN-002 | Demonstrated locallyFeeds and devices | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR056 Keep live activation explicit | Chapter 17 · 17.3REQ-DATA-FOUNDATION-009 | Explained onlyFeeds and devices | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR057 Track quality issues and corrections | Chapter 7 · 7.7REQ-AUD-003 | Demonstrated locallyShared objects; Source claims and identity | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR058 Apply published field rules | Chapter 7 · 7.2REQ-DATA-FOUNDATION-001 | Partial demonstrationSource claims and identity | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR059 Review candidate identity links | Chapter 7 · 7.5REQ-DATA-FOUNDATION-007; REQ-REVIEWED-JOIN-001 | Demonstrated locallySource claims and identity | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR060 Keep differing values from each source | Chapter 7 · 7.6REQ-DATA-FOUNDATION-002 | Demonstrated locallySource claims and identity | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR061 Limit preferred source decisions | Chapter 7 · 7.6REQ-DATA-FOUNDATION-007 | Demonstrated locallySource claims and identity | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR062 Reuse the quality worklist | Chapter 7 · 7.7REQ-DATA-FOUNDATION-009 | Demonstrated locallySource claims and identity | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR063 Describe spatial sources | Chapter 10 · 10.4REQ-GIS-001 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR064 Save permitted map settings | Chapter 10 · 10.11REQ-GIS-002 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR065 Reuse one spatial catalogue | Chapter 10 · 10.4REQ-GIS-003 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR066 Protect location disclosure | Chapter 10 · 10.5REQ-GIS-004 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR067 Exclude known demonstration features | Chapter 10 · 10.4REQ-GIS-DATA-001 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR068 Keep navigation and large maps simple | Chapter 10 · 10.2REQ-INT-003; REQ-INT-004 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR069 Provide bounded vector exploration | Chapter 10 · 10.7REQ-GIS-ADV-002 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR070 Use genuine points for point methods | Chapter 10 · 10.7REQ-GIS-ADV-003 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR071 Compare compatible raster cells | Chapter 10 · 10.7REQ-GIS-ADV-004 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR072 Retain an exploratory receipt | Chapter 10 · 10.7REQ-GIS-ADV-005; REQ-GIS-ADV-006 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR073 Retain normalized spatial sources | Chapter 10 · 10.7REQ-GIS-DATA-002; REQ-GIS-DATA-003 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR074 Review spatial release separately | Chapter 10 · 10.4REQ-GIS-DATA-004; REQ-GIS-DATA-005; REQ-DOC-005 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR075 Keep weather source identities | Chapter 11 · 11.5REQ-PMU-OPS-011; REQ-LIVE-EVIDENCE-001 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR076 Show missing and stale weather honestly | Chapter 11 · 11.11REQ-PMU-OPS-011 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR077 Keep retained rainfall at its actual scale | Chapter 11 · 11.5REQ-GN-RAIN-002 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR078 Do not invent the GN time series | Chapter 11 · 11.5REQ-GN-RAIN-002; REQ-DSS-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR079 Separate evidence from warnings | Chapter 11 · 11.5REQ-DSS-001; REQ-INT-005 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR080 Keep farming identities and plots | Chapter 5 · 5.3REQ-PMU-OPS-004 | Partial demonstrationProducts and enterprises | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR081 Record farm work and issues | Chapter 6 · 6.3REQ-PMU-OPS-004 | Partial demonstrationProducts and enterprises | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR082 Keep harvest and sale evidence | Chapter 15 · 15.6REQ-PMU-OPS-004 | Demonstrated locallySupply and buyer demand; Payment evidence | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR083 Keep origin and currency explicit | Chapter 15 · 15.5REQ-PMU-OPS-004; REQ-PMU-OPS-008 | Partial demonstrationSupply and buyer demand | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR084 Compare only compatible market evidence | Chapter 15 · 15.4REQ-PMU-OPS-009 | Demonstrated locallySupply and buyer demand | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR085 Use accepted seasonal arithmetic | Chapter 15 · 15.7REQ-DSS-001; REQ-MON-012 | Demonstrated locallyCalculation methods; Supply and buyer demand | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR086 Reuse participant identities | Chapter 14 · 14.6REQ-PMU-OPS-001 | Demonstrated locallyPeople and households; Participation and support | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR087 Record support and training history | Chapter 14 · 14.5REQ-PMU-OPS-002 | Demonstrated locallyPeople and households; Participation and support | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR088 Connect products producers and buyers | Chapter 15 · 15.1REQ-PMU-OPS-003 | Demonstrated locallyProducts and enterprises; Supply and buyer demand | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR089 Keep livelihood outcomes separate | Chapter 14 · 14.6REQ-PMU-OPS-004 | Demonstrated locallyProducts and enterprises | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR090 Reuse asset and connection records | Chapter 5 · 5.5REQ-PMU-OPS-005 | Partial demonstrationEcosystem service schemes | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR091 Retain handover and maintenance evidence | Chapter 20 · 20.9REQ-PMU-OPS-005 | Partial demonstrationEcosystem service schemes | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR092 Keep PES frameworks controlled | Chapter 15 · 15.9REQ-PMU-OPS-006 | Demonstrated locallyEcosystem service schemes; Service agreements; Service verification; Payment evidence | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR093 Trace programme connections | Chapter 13 · 13.2REQ-PMU-OPS-007 | Demonstrated locallyService verification | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR094 Build reusable report questions | Chapter 9 · 9.6REQ-QRY-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR095 Keep report sources and access rules | Chapter 9 · 9.11REQ-QRY-002 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR096 Review how datasets will be combined | Chapter 9 · 9.5REQ-REVIEWED-JOIN-001 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR097 Show unmatched and invalid inputs | Chapter 9 · 9.8REQ-REVIEWED-JOIN-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR098 Save report definitions and results | Chapter 9 · 9.10REQ-EXPERT-REPORT-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR099 Use suitable visuals and source maps | Chapter 9 · 9.7REQ-EXPERT-VIS-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR100 Export reports with sources and review history | Chapter 9 · 9.11REQ-RPT-001; REQ-EXPERT-REPORT-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR101 Show what a decision needs | Chapter 12 · 12.2REQ-DSS-001 | Partial demonstrationDecision cases | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR102 Calculate an approved criteria score | Chapter 12 · 12.5REQ-DSS-001 | Demonstrated locallyDecision cases; Calculation methods | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR103 Check differences and thresholds safely | Chapter 12 · 12.3REQ-DSS-001 | Demonstrated locallyDecision cases; Calculation methods | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR104 Route a reviewed finding only when configured | Chapter 12 · 12.10REQ-DSS-002 | Partial demonstrationDecision cases | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR105 Record the human decision | Chapter 12 · 12.8REQ-DEC-010 | Demonstrated locallyRisks and corrective actions; Decision cases | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR106 Use actual evidence and current guidance | Chapter 12 · 12.6REQ-CF-001; REQ-CF-002 | Partial demonstrationDecision cases | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR107 Require independent review and approved methods | Chapter 12 · 12.9REQ-CF-003; REQ-DSS-003 | Partial demonstrationDecision cases | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR108 Register the programme or project | Chapter 13 · 13.1REQ-PRJ-001 | Demonstrated locallyProjects | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR109 Connect domains and areas once | Chapter 13 · 13.2REQ-PRJ-002 | Partial demonstrationProjects | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR110 Organize implementation | Chapter 13 · 13.3REQ-PRJ-003 | Partial demonstrationProjects; Implementation feasibility | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR111 Link project evidence | Chapter 13 · 13.7REQ-PRJ-004 | Demonstrated locallyMy work | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR112 Onboard ongoing and completed projects | Chapter 13 · 13.1REQ-PRJ-005 | Partial demonstrationProjects | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR113 Keep versions of major project changes | Chapter 13 · 13.1REQ-PRJ-006 | Partial demonstrationProjects | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR114 Follow the project from setup to closure | Chapter 13 · 13.13REQ-LCY-001 | Partial demonstrationProjects | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR115 Record each project step and its owner | Chapter 13 · 13.5REQ-LCY-002; REQ-LCY-003 | Demonstrated locallyRecurring work | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR116 Keep task submissions and review records linked | Chapter 13 · 13.7REQ-DEL-001 | Demonstrated locallyMy work | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR117 Generate scheduled tasks once | Chapter 13 · 13.4REQ-DEL-002 | Demonstrated locallyRecurring work | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR118 Record who must deliver each item | Chapter 13 · 13.5REQ-DEL-003 | Partial demonstrationRecurring work; Risks and corrective actions | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR119 Return and correct with a reason | Chapter 13 · 13.7REQ-DEL-004 | Demonstrated locallyMy work | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR120 Show only permitted assigned work | Chapter 13 · 13.5REQ-DEL-005 | Partial demonstrationRecurring work; My work | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR121 Keep required review independent | Chapter 13 · 13.7REQ-WF-005; REQ-WF-006 | Partial demonstrationMy work | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR122 Connect protected feedback to action | Chapter 14 · 14.7REQ-SHARED-COMP-003 | Demonstrated locallyFeedback and requests | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR123 Approve the monitoring plan | Chapter 13 · 13.8REQ-MON-011 | Partial demonstrationMonitoring and indicators | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR124 Allow honest baseline and target states | Chapter 13 · 13.8REQ-SHARED-COMP-001 | Demonstrated locallyMonitoring and indicators | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR125 Execute a repeatable reviewed method | Chapter 13 · 13.8REQ-MON-012 | Partial demonstrationMonitoring and indicators; Calculation methods | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR126 Reconcile closure across the project | Chapter 13 · 13.13REQ-CLS-001 | Partial demonstrationRisks and corrective actions | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR127 Verify or waive each closure check properly | Chapter 13 · 13.13REQ-CLS-002 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR128 Allow closure only after required checks | Chapter 13 · 13.13REQ-CLS-003 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR129 Catalogue documents and media | Chapter 14 · 14.11REQ-DOC-001 | Demonstrated locallyKnowledge library; Documents and extraction | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR130 Protect originals and derived files | Chapter 8 · 8.2REQ-DOC-002 | Explained onlyDocuments and extraction | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR131 Scan and authorize file use | Chapter 6 · 6.5REQ-DOC-003; REQ-DOC-004 | Explained onlyDocuments and extraction | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR132 Review knowledge publication | Chapter 14 · 14.11REQ-KNW-001 | Demonstrated locallyKnowledge library | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR133 Retain eligible citations | Chapter 14 · 14.11REQ-KNW-002; REQ-CF-002 | Partial demonstrationKnowledge library | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR134 Offer a simple beneficiary view | Chapter 14 · 14.1REQ-BEN-001; REQ-BEN-002 | Partial demonstrationParticipation and support; Knowledge library; Verified account links | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR135 Keep anonymous intake closed until approved | Chapter 14 · 14.7REQ-SHARED-COMP-004 | Partial demonstrationFeedback and requests; Public feedback policy | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR136 Use the API for all web actions | Chapter 4 · 4.6REQ-WEB-001 | Explained onlyFeedback and requests; Public feedback policy | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR137 Keep workflows simple and accessible | Chapter 16 · 16.1REQ-WEB-002; REQ-WEB-004 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR138 Use approved choices and language resources | Chapter 16 · 16.9REQ-WEB-003 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR139 Protect mobile sign in | Chapter 16 · 16.7REQ-MOB-001; REQ-MOB-002 | Explained onlyArchitecture / operating explanation | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR140 Capture permitted field evidence | Chapter 16 · 16.7REQ-MOB-003; REQ-MOB-004 | Explained onlyArchitecture / operating explanation | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR141 Show the sending status of offline records | Chapter 16 · 16.8REQ-MOB-005; REQ-MOB-006 | Explained onlyArchitecture / operating explanation | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR142 Explain the architecture through real workflows | Chapter 16 · 16.2REQ-ARCH-EXPLORER-001 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR143 Expose controlled API contracts | Chapter 17 · 17.2REQ-API-001 | Explained onlyArchitecture / operating explanation | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR144 Bound work and return safe errors | Chapter 18 · 18.1REQ-API-002; REQ-API-003 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR145 Prevent duplicate requests and conflicting edits | Chapter 17 · 17.9REQ-API-004 | Demonstrated locallyShared map, report, provider or dashboard workflow | The relevant local model/workflow is exercised; production data and institutional acceptance remain separate. |
| FR146 Protect transport and endpoints | Chapter 18 · 18.4REQ-API-005 | Explained onlyArchitecture / operating explanation | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR147 Use approved operations to access data | Chapter 4 · 4.7REQ-API-006 | Explained onlyArchitecture / operating explanation | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR148 Keep action history and source links | Chapter 8 · 8.9REQ-AUD-001; REQ-AUD-002 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR149 Protect discovery and notification delivery | Chapter 18 · 18.5REQ-AUD-004 | Partial demonstrationShared map, report, provider or dashboard workflow | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR150 Govern change and trace requirements | Chapter 21 · 21.10REQ-GOV-002; REQ-GOV-003; REQ-GOV-004 | Partial demonstrationPending decisions; Requirements and changes | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
| FR151 Separate environments and secrets | Chapter 20 · 20.5REQ-OPS-001 | Explained onlyRequirements and changes | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR152 Monitor service health without exposing private data | Chapter 18 · 18.10REQ-OPS-002 | Explained onlyRequirements and changes | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR153 Release through controlled runbooks | Chapter 20 · 20.5REQ-OPS-003 | Explained onlyRequirements and changes | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR154 Prove coordinated recovery | Chapter 18 · 18.9REQ-OPS-004 | Explained onlyRequirements and changes | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR155 Separate web and shared service hosting responsibilities | Chapter 4 · 4.5REQ-OPS-005 | Explained onlyRequirements and changes | The required real service or operating control is explained; this static prototype cannot prove its acceptance. |
| FR156 List software gaps and missing external decisions separately | Chapter 21 · 21.8REQ-SHARED-COMP-005; REQ-SHARED-COMP-006 | Partial demonstrationRequirements and changes | A related screen/model exists; the complete source acceptance condition still needs real data, integration or targeted verification. |
The audit tested an isolated browser session and the current embedded models. No existing records were edited. Private original SHARED access, real mobile devices, certified language review, institutional sign-off, production load/security tests and coordinated recovery are not established by these checks.
Keep the original business outcomes: collect and check information; reuse the same identity; compare suitable evidence; record decisions and actions; follow results; and return useful information to contributors. A public snapshot, sample chart or advice acceptance does not replace an approved institutional decision.