Source identity
| Field | Recorded value |
|---|---|
| Source type | GitHub source |
| Original record | Janady13/thatstupidcomputer / docs/standards/README.md |
| Date | Not specified in source |
| Repository | Janady13/thatstupidcomputer |
| Revision | 57555cde46910102dd25d6c1c1fb2c359e9655bd |
| Branch | main |
| Path or archive member | docs/standards/README.md |
| Original SHA-256 | ff0122a016aa07d1deadcf9090b6860d59f3138bb8a73d9fc236dce44879c9a6 |
| Git blob SHA | 4df1a215aa945b89f0d90f43543d0bda34c94d4d |
| Reading-copy SHA-256 | ff0122a016aa07d1deadcf9090b6860d59f3138bb8a73d9fc236dce44879c9a6 |
Recovered source transcript
Download complete source text ↓60 lines · 7.8 KB
# Private standards coverage and separate review
This directory is an implementation ledger for the supplied SEO/AIO library. It is private handoff material and must never be copied into the web document root. The library governs this complete React website through explicit requirements, evidence and applicability decisions; it is not a collection of marketing copy to publish.
`coverage-ledger.json` accounts for all **135 supplied document records, 26 role charters and 40 graph cards**, with source hashes, locators, requirement owners, implementation paths and verification conditions. `decisions.json` records user overrides, conditional graph decisions and the 28 supplied source-conflict dispositions. `observations.json` records the separate review and actual local tests. Read the observations before interpreting any implementation status.
The combined TXT contains 895,559 bytes; the separately recovered graph expansion contains 117,476 bytes and is also present in that combined TXT. The catalog references **146 original legacy files whose complete bodies were not supplied**. The inventory retains every catalog reference and its reported treatment without claiming to have read or certified those missing originals or the absent companion JSON/utility files. All supplied document bodies and graph cards were reviewed in bounded reads, suppressing exact lines already read where repeated. Structural ingestion checks the complete bytes; keyword presence never establishes compliance.
## Which instruction controls
1. The user's current task and corrections control: build the entire site locally; React; no Python; no PostgreSQL or lead database; direct email; consume the existing unified canonical truth source; deliver a portable Claude Code handoff.
2. The source library's current source-linked charters, release contracts, graph cards and rewritten guides govern relevant implementation. Their source dates are retained; version-sensitive platform claims still need current primary-source checks.
3. Patched legacy guidance can supply transferable principles only where it does not conflict with those current instructions. The original archive is unavailable.
4. Historical validation reports describe that library package, not this website. Unapproved publication briefs, methodology drafts, synthetic examples and candidate host/identity plans are review material, not approved public claims.
Next.js framework APIs and Python utilities are explicitly superseded for this project. Their useful rendering, metadata, evidence and structural-check principles are implemented through React and Node. Optional queue/database examples cannot override the user's direct-email/no-database instruction. Shape validation and digest pins cannot confer factual truth or publication permission.
## Applicability is reasoned, not a feature quota
The ledger's `requirements` provide the implementation/verification contract. Every document and graph maps into that contract with a reason. `graphIds` on a document means shared requirement coverage, not that the source document itself names every associated graph. Role identifiers describe accountable review concerns; they do not claim 26 people, qualifications or external auditors worked on the site.
| Treatment | Meaning in this project |
| --- | --- |
| `APPLY` | Relevant requirement, with implemented paths and actual behavior to verify. |
| `PARTIAL` | Transferable principles apply; explicitly incompatible framework/utility details do not. |
| `CONDITIONAL` | Apply evidence and omission controls now; activate the feature only when real scope, facts or account access exist. |
| `REVIEW_ONLY` | Useful methodology or unapproved draft; do not publish it as completed work or add an unrequested product. |
| `HISTORICAL_RECORD` | Retain provenance and supersession context; never inherit a product PASS. |
| `NOT_APPLICABLE` | Specific feature is outside the authorized site and a recorded reason explains why. Missing necessary access is never hidden under this label. |
Commerce/merchant feeds (G06), translated-equivalent hreflang (G18), an owned GraphRAG product (G27), a vector/embedding search product (G28), scholarly publication (G38) and ticketed events (G39) are outside this service-to-inquiry website. A requested demo is not an Event. Multimedia provenance (G35) applies because the site actually contains SVG, Rive and sharing artwork. Local branches, testimonials, profile edits, external citations and live account observations remain conditional or unavailable; none are fabricated for graph completeness. Private handoff/training material does not imply a public course or mass-published role pages.
## Acceptance boundaries
The inventory initializes broad behavioral requirements as `PENDING`. Specific executed checks and their exact scope appear in `observations.json`; a test's PASS does not automatically pass every requirement associated with its source documents. `NOT_APPLICABLE` is an applicability decision, not a test result. Source-file existence, counts, hashes, valid JSON and historical reports are structural evidence only.
The separate review is by another AI task worker with shared context and filesystem. It is distinct from the code owners' own checks, but is **not independent human or external audit certification**. No manual accessibility, device, mailbox, account or field-performance observations are invented. The root acceptance file remains the whole-build record; these records provide the narrower standards and code-review evidence behind it.
| Still requires actual external/environment evidence | Why local implementation cannot certify it |
| --- | --- |
| Canonical truth export and approved public identity | Actual upstream registry/export is absent. Production build must fail closed until a reviewed full commit and exact export digest are supplied. Test fixtures cannot replace it. |
| Browser layout, keyboard/reflow, screen reader and runtime interaction | This execution environment's browser URL policy blocks the local test target and forbids alternate browser workarounds. Portable tests and manual checks are handed off for an authorized target. Node/fake-DOM or native Canvas runs are labeled with their limited scope. |
| SMTP receipt and sender authentication | Fake transport tests prove application response behavior; provider acceptance is not mailbox delivery, destination folder or human reading. |
| Live GA4 wire/DebugView, property configuration and search reports | No authorized production accounts or consented traffic observations were supplied. Missing values remain unavailable rather than zero. |
| Public BUBBLES cutover, DNS/TLS, rollback and indexing | No actual host release or public edge observation is performed by this review. A working local package does not establish those outcomes. |
| Field Core Web Vitals and business outcomes | Asset budgets and laboratory checks are not consented field distributions, qualified inquiries, revenue or causal uplift. |
## Reproduce and maintain
From the project root on Node 24:
```bash
node scripts/standards-inventory.ts
node scripts/standards-inventory.ts --check
```
The first command regenerates mappings and current path-existence observations. The second checks supplied-source drift, completeness and saved mapping structure. Neither makes a network request, invokes Python, installs packages, mutates the canonical truth source, sends email or grants permission to publish.
When a source or implementation changes, follow the requirement-to-path mapping and rerun the affected behavior checks. Record the command, environment, timestamp, tested hashes, result and limitations. Preserve failed or blocked evidence instead of converting missing evidence into success. Review current official provider guidance again before a version-sensitive release decision. Do not turn this maintenance instruction into an unrequested scheduler or retrieval service.