ChatGPT Interfaces — Requirements and Scope v0.1.44
Status: Recovered historical inventory and proposed proportionality revision. Not an accepted implementation/verification baseline.
This register is the current packaged index for the recovered PEND-001–PEND-061 descriptions. Original historical documents are retained separately. The earlier PEND-001 identifier collision is unresolved; do not merge the two meanings.
| ID | Historical phase | v0.1.42 release classification | Proposed treatment | Requirement |
|---|---|---|---|---|
| PEND-001 | Deployment safety & data; phase 4 | DEFERRED | SIMPLIFY | Keep two verified historical snapshots of complete chatgpt-interface-data, before each successful update, independently of ZIP retention; retain originals until replacement verified |
| PEND-002 | Deployment safety & data; phase 4 | DEFERRED | SIMPLIFY | Admin list/select/restore data snapshots, with timestamp, version, hash, size, confirmation, protective current-data backup and audit |
| PEND-003 | Deployment safety & data; phase 4 | DEFERRED | SIMPLIFY | Verify data backup rotation under three deployments and simulated backup/deployment failure |
| PEND-004 | Deployment safety & data; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Independently install/verify external updater and remove ambiguous divergent bundled updater copies |
| PEND-005 | Deployment safety & data; phase 3 | STAGING_OR_LIVE | RETAIN | Full end-to-end administrator rollback test on representative staging, including deliberate rollback after successful deployment |
| PEND-006 | Deployment safety & data; phase 3 | STAGING_OR_LIVE | SIMPLIFY | Fault injection for interrupted update, failed backup, failed activation, failed rollback, failed restoration, corrupt archives and permissions |
| PEND-007 | Deployment safety & data; phase 3 | STAGING_OR_LIVE | RETAIN | Verify retained-installation restore integrity and persistent-data isolation on real server |
| PEND-008 | Deployment safety & data; phase Future | DEFERRED | RETAIN | Provide recovery from archived release ZIP when no retained installation directory exists |
| PEND-009 | Deployment safety & data; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Preserve last-known-good backup until verified replacement, unique temporary paths, fail-closed filesystem operations |
| PEND-010 | Deployment safety & data; phase 3 | STAGING_OR_LIVE | RETAIN | Validate v0.1.34-to-new-version lineage on installed updater before distribution |
| PEND-011 | Deployment safety & data; phase Future | DEFERRED | SIMPLIFY | Provide authoritative deployment-state API: file paths/sizes/hashes, release, source commit and post-deployment validation |
| PEND-012 | Deployment safety & data; phase Future | DEFERRED | SIMPLIFY | Distinguish installed/deployed, GitHub and latest retained/generated version and report drift |
| PEND-013 | Documentation content; phase 3 | MANDATORY_PACKAGE | RETAIN | Rewrite System Specification as complete current architecture, PHP entry points, dependencies, data model, auth, APIs, error handling, deployment and limits; separate release history |
| PEND-014 | Documentation content; phase 3 | MANDATORY_PACKAGE | RETAIN | Rewrite Functional Specification as complete behavior/inputs/outputs/roles/validation/errors, excluding acceptance basis |
| PEND-015 | Documentation content; phase 3 | MANDATORY_PACKAGE | RETAIN | Rewrite User Guide with task-based purpose, prerequisites, field-level instructions, success, errors and recovery |
| PEND-016 | Documentation content; phase 3 | MANDATORY_PACKAGE | RETAIN | Rewrite Administrator Guide with complete credential creation, repository enrollment, client assignments, verification, revocation and recovery procedures |
| PEND-017 | Documentation content; phase 3 | MANDATORY_PACKAGE | RETAIN | Verify API Reference against actual endpoints with full schemas, HTTP errors and executable curl examples |
| PEND-018 | Documentation content; phase 3 | MANDATORY_PACKAGE | RETAIN | Provide readable navigation with Back to Documentation on every HTML page, section links, bullets, spacing and responsive design |
| PEND-019 | Documentation content; phase 3 | STAGING_OR_LIVE | SIMPLIFY | Prove HTML/DOCX/Markdown parity for every required document; visually inspect rendered pages |
| PEND-020 | Documentation content; phase 3 | MANDATORY_PACKAGE | RETAIN | Move acceptance basis to separate Verification and Acceptance Plan |
| PEND-021 | Documentation content; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Reconcile cumulative release notes per version against every shipped feature, defect fix, doc change and backlog ID; newest first |
| PEND-022 | Documentation content; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Reconstruct older release history from evidence, label uncertain history, never invent entries |
| PEND-023 | Documentation content; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Make documentation audit meaningful and comprehensive, not only file/keyword presence |
| PEND-024 | Documentation content; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Provide human-readable HTML audit dashboard with clickable per-document findings, severity, corrections, metadata and navigation |
| PEND-025 | Documentation content; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Audit HTML/JSON parity and require explicit NOT VERIFIED for checks needing human review |
| PEND-026 | Test and release controls; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Release Test Report: dashboard counts PASS/FAIL/BLOCKED/NOT RUN/NOT APPLICABLE and linked test detail/back links |
| PEND-027 | Test and release controls; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Per test: objective, requirement ID, prerequisites, exact package hash/commit, environment, procedure, expected/actual, logs, duration, result and retest history |
| PEND-028 | Test and release controls; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Coverage matrix across unit/integration/regression/deployment/documentation/live acceptance with untested requirements visible |
| PEND-029 | Test and release controls; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Generate human-readable HTML report and machine-readable results from same authoritative test run |
| PEND-030 | Test and release controls; phase 3 | MANDATORY_PACKAGE | RETAIN | Release Specification direct links to current Acceptance Test Plan and Acceptance Test Report |
| PEND-031 | Test and release controls; phase 4 | DEFERRED | SIMPLIFY | Phase 4 links to Automated Unit Test Specification and Automated Unit Test Report |
| PEND-032 | Test and release controls; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Automated release gate requiring every mandatory requirement linked to implementation and passing evidence; fail on incomplete or unverified |
| PEND-033 | Test and release controls; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Independently review semantic document usefulness, not merely generated-file existence |
| PEND-034 | Test and release controls; phase 3 | STAGING_OR_LIVE | RETAIN | Retest all Stage 1/2 accepted functions against changed release |
| PEND-035 | Test and release controls; phase 3 | STAGING_OR_LIVE | RETAIN | Execute actual live acceptance and record user decision separately from local/static tests |
| PEND-036 | Test and release controls; phase 4 | DEFERRED | RETAIN | Create automated PHPUnit unit, integration and browser regression test suite before broad engineering cleanup |
| PEND-037 | Test and release controls; phase 4 | DEFERRED | SIMPLIFY | Independent security, complexity, architecture, permissions, UI, recovery and data integrity inspection; fix critical issues |
| PEND-038 | Backlog & handoff; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Comprehensive authoritative backlog with permanent IDs, priority, status, phase, dependencies, acceptance and evidence |
| PEND-039 | Backlog & handoff; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Backlog HTML dashboard counts, clickable entries and detailed record; DOCX parity |
| PEND-040 | Backlog & handoff; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Reconcile backlog at every release/handoff as UPDATED/ALREADY CURRENT/INCOMPLETE with evidence |
| PEND-041 | Backlog & handoff; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Publish cumulative self-contained handoff, status dashboard and authoritative references on website and Library |
| PEND-042 | Backlog & handoff; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Handoff three independent download links: currently deployed, latest available, last accepted, with hashes/dates |
| PEND-043 | Backlog & handoff; phase 3 | STAGING_OR_LIVE | SIMPLIFY | Fresh-session restart acceptance test using only handoff and backlog |
| PEND-044 | Backlog & handoff; phase 3 | MANDATORY_PACKAGE | RETAIN | Preserve immutable versioned historical packages; never silently overwrite changed bytes |
| PEND-045 | Backlog & handoff; phase 3 | MANDATORY_PACKAGE | SIMPLIFY | Complexity scoring for each planned change (5 dimensions, 1–5, score bands and review triggers) |
| PEND-046 | GitHub source control; phase Future | DEFERRED | RETAIN | Verify retained ZIP reuse across Compare, Initial Import and Synchronize |
| PEND-047 | GitHub source control; phase Future | DEFERRED | RETAIN | Make Synchronize controlled bootstrap; established repository changes must be explicit Git commits |
| PEND-048 | GitHub source control; phase 5 | DEFERRED | RETAIN | Exact-revision reads and diff/compare API primitives for AI clients |
| PEND-049 | GitHub source control; phase 5 | DEFERRED | RETAIN | Authorized GitHub branch creation and scoped atomic multi-file commits |
| PEND-050 | GitHub source control; phase 5 | DEFERRED | SIMPLIFY | Expected-HEAD optimistic concurrency, stale-base rejection and conflict/reconciliation flow |
| PEND-051 | GitHub source control; phase 5 | DEFERRED | SIMPLIFY | Machine-readable write audit with resulting commit SHA and actionable errors |
| PEND-052 | GitHub source control; phase 5 | DEFERRED | RETAIN | Keep GitHub PATs server-side; enforce repository and operation scopes |
| PEND-053 | GitHub source control; phase Future | DEFERRED | SIMPLIFY | Discoverable capabilities endpoint and matching human-facing capabilities view |
| PEND-054 | GitHub source control; phase Future | DEFERRED | SIMPLIFY | Multi-AI client compatibility and independent second-AI integration acceptance test |
| PEND-055 | GitHub source control; phase Architecture | DEFERRED | RETAIN | Retain narrow AI-to-GitHub bridge scope rather than IDE functionality |
| PEND-056 | Domain manifest & integration; phase Future | DEFERRED | RETAIN | Create versioned Domain Manifest schema with identity, resources, schemas, endpoints, instructions, authority and access |
| PEND-057 | Domain manifest & integration; phase Future | DEFERRED | RETAIN | Create registry with stable bootstrap, register/list/get/update/version/validate manifests |
| PEND-058 | Domain manifest & integration; phase Future | DEFERRED | SIMPLIFY | Enforce domain manifest access permissions and exact version/hash reporting |
| PEND-059 | Domain manifest & integration; phase Future | DEFERRED | RETAIN | Migrate KIP Apiary bootstrap instructions into KIP domain manifest |
| PEND-060 | Domain manifest & integration; phase Architecture | DEFERRED | RETAIN | Keep KIP as durable domain-state owner and GitHub as source-history owner |
| PEND-061 | Domain manifest & integration; phase 6 | DEFERRED | RETAIN | Complete Phase 6 KIP feature workflow from source read through test, commit, unique ZIP and user acceptance |
Proportionality decision
34 of the 61 requirements have proposed scope reductions; 27 retain their earlier intent. Proposed simplification is not evidence of implementation or formal acceptance. Keep authentication, credential protection, ZIP integrity, recoverable backups, and rollback.
Source and limitations
Recovered descriptions originate from the historical inventory preserved in the cumulative development handoff. They were not independently checked against every original conversation. Package implementation and live acceptance must be evaluated separately.