# PentaScope master reference pack

> SYNTHETIC REFERENCE • SAMPLE-PENTASCOPE-MASTER • v1.0.0 • 2026-09-08 • Draft • all 96 cases Not Run. This is a proposed learning and acceptance pack, not customer source truth, test evidence or release approval. No project is created or seeded by opening it.

Open **index.html** in a browser to read, search and print the entire reference offline. The published application path is `/samples/master-app/index.html`. It makes no API calls and contains no credentials. English is the main authoring language; Arabic fixtures and a short Arabic walkthrough are included.

## What is included

- **BRD.md** — business purpose, stakeholders, scope, goals, rules, assumptions, priorities and risks.
- **SRS.md** — 32 detailed requirements and user stories, 96 acceptance criteria, data dictionary, roles, workflows, integrations and proposed NFRs.
- **TEST-CASES.md** — 96 full manual test designs with setup, ordered actions, expected results, evidence and cleanup.
- **EXECUTION-PLAN.md** — entry/exit gates, roles, sequencing, exact-build execution, result definitions and evidence contract.
- **execution-manifest.json**, **execution-log.csv**, **execution-step-log.csv** — unfilled run templates with case IDs and Not Run statuses.
- **DEFECTS-RETEST.md**, **defect-template.json**, **release-decision-template.json** — defect, retest and release review templates without invented observations.
- **USER-GUIDE.md** — practical adoption and role walkthrough, troubleshooting and glossary.
- **traceability.csv**, **test-cases.csv**, **sample.json**, **source-manifest.json**, **gaps-decisions.csv** — machine-readable reference data.

## Read and use in order

1. Read BRD and the open decisions. Confirm whether this proposed PentaScope scope fits the project you intend to test.
2. Review SRS and the exact criterion-to-case links. Keep unsupported claims classified as recommendations or gaps.
3. Make a copy of the pack for a disposable sandbox. Bind real project-owned source/version IDs and record your own approval decisions. Sample JSON is not a direct runtime API payload.
4. Complete the execution manifest and approve a safe scope. Use local provider, mail and webhook fixtures unless external use is explicitly authorized.
5. Execute the cases, record actual observations and evidence, triage defects, retest the same delivered build and make a named release decision.

## Coverage truth

The authored functional design has 32 business rules, 32 requirements/stories and 96 explicitly linked criteria/cases. Designed link coverage is 100% of **this authored functional set**. Approved, executed and passed coverage are all 0%. There are no observed defects or evidence files. Numeric performance, retention and recovery objectives are still open decisions; neither complete production coverage nor release readiness is claimed.

## Maintainer regeneration

Run `python3 build_sample.py` in this directory to rebuild local/static files, then `python3 validate_sample.py`. The builder uses local sources only, never invokes AI or the application, and never writes project records. Source hashes describe the local working tree at generation time; rerun after adopted behavior changes. Frontend/public contains the same reader artifacts, not executable app state.