WAP 1.2.1 / WML 1.3 Planning Baseline

Version: v1.0

Planning status: complete for the selected strict profile

Implementation status: pre-conformance

Purpose

This document is the closure checkpoint for source ingestion, specification selection, obligation extraction, implementation mapping, and work planning. It does not claim that the browser is compliant.

The target is the exact WAP-215 Class C data-client profile CCR-CLASSC-C-001, with WAP 1.2.1 and WML 1.3 observable behavior as the strict compatibility floor. Modern internals and additive features are allowed only when they preserve strict results or are isolated behind an explicit capability/mode.

Planning closure

Control plane	Closed planning state
Release source	97/97 technical members have verified private PDFs and non-empty text extractions; 21 are already canonical and 76 remain outside Git pending redistribution guidance
Class selection	WAP-215’s six Class A/B/C client/server graphs are extracted; CCR-CLASSC-C-001 is the declared first-release profile
Effective specifications	Every selected family has an ordered base/SIN chain and successor sources cannot silently replace the target release
Selected obligations	712 effective source rows reduce to 198 selected parent rows across nine mandatory families
Nested clauses	The 198 parents expand into 762 clauses: 722 required, 29 recommended, and 11 permitted
Crosswalk	Every selected parent has source anchors, strict disposition, requirement IDs, owner layers, work items, and an evidence state
Fixtures	All 762 clause fixtures have target locations; 364 clauses now have direct conformance assessment and 398 remain unassessed
Successor delta	All 198 selected rows are classified; 17 have successor-derived foundations, with 2 compatible and 15 requiring strict correction
External dependencies	43 authority-locked dependencies have 48 private artifacts; 60 residual labels are explicitly non-blocking for Class C and profile-activated
Execution program	13 dependency-ordered sprints contain 83 unique work items plus the machine-checked TRN-7-CL-C selected-profile completion gate

SRC-006 is the only blocked source item. All 97 technical members are available for private extraction, and the 106-entry redistribution inventory and request package are maintainer-ready. The gate now prevents public promotion of recovered source binaries/derivatives until outreach is approved and written permission is received; it does not block internal evidence use, implementation, or fixture construction.

Conservative implementation snapshot

Parent-level status is an audit snapshot, not a compliance percentage:

Family	Selected parents	Clauses	Implemented	Partial	Missing
WML	39	175	23	10	6
WAE	11	39	5	3	3
WBXML	3	47	0	3	0
WMLScript	41	107	0	32	9
WMLScript Libraries	80	211	0	21	59
Caching	5	68	0	3	2
WDP	9	49	9	0	0
WCMP	2	9	2	0	0
WSP	8	57	8	0	0
Total	198	762	47	72	79

Parent-row status is not a substitute for direct clause evidence. With 364 of 762 clauses assessed, the project remains pre-conformance until every selected obligation is implemented or retains an explicit, release-blocking gap.

Work-program state

The 83 work items currently roll up to:

• 32 done (source/profile/governance planning, the direct WDP/WCMP slices including TRN-708 and TRN-710, the completed WSP-801/WSP-802 connectionless matrices, the WML-2/WML-205 closure, WML-302 variable/substitution closure, WML-303 action/event/BACK closure, WML-304 request-pipeline closure, WML-305 native timer closure, WML-306 policy closure, WML-309 frame-affordance closure, the additive WMLS-501 verifier closure, and the frontend production-build defect closure);
• 1 blocked (SRC-006, external redistribution permission);
• 10 in progress (existing runtime, the bounded WMLS-502 executor with broader parent/remaining-clause follow-through, the WML-301 aggregate WAE-delegate follow-through, WAE, transport, and WSP foundations);
• 40 todo, including additive WML-307 character-processing/generic-WBXML residual closure without reopening WML-203 and WML-308 form-control presentation/capability residual closure without reopening WML-305.

New completion claims should follow the machine dependency graph:

1. Preserve the completed WML-2 baseline while TRN-7 continues after the completed CONF-1 planning gate.
2. Preserve completed WML-302, WML-303, and WML-305 while advancing the remaining WML-3 work after WML-2.
3. Complete REN-4 and WMLS-5 after WML-3.
4. Complete WAE-6 after runtime, rendering, and script dependencies.
5. Advance the selected connectionless WSP-8 path after the completed TRN-7-CL-C profile gate, and complete it after WAE-6; dormant WTP work does not gate this path.
6. Close native/WASM/end-to-end evidence in INT-9.
7. Apply the strict compatibility and build gate in REL-10.
8. Activate OPT-11 profiles and ENH-12 improvements only after the strict release gate, unless work is isolated research that cannot alter strict behavior.

Existing work in a downstream sprint may provide a foundation, but the sprint cannot be declared complete before its upstream gates.

Intentional non-blocking queues

These are bounded activation gates, not missing selected-profile planning:

• 60 residual external citations: 3 optional/informative content or language labels, 45 non-selected bearer/radio labels, and 12 optional WTLS crypto labels;
• WAP-237 optional media and later OMA follow-on successor deltas;
• effective WTP extraction and evidence, activated only when connection-oriented WSP is claimed;
• optional WTLS, WIM, Push, WTA/WTAI, UAProf, WMLScript Crypto, and other declared capability profiles;
• public source promotion after explicit redistribution/derivative approval.

Activating one of these capabilities must activate its source, obligation, fixture, and release-evidence gates. It must not silently expand the Class C claim.

Remaining implementation outcome

The remaining build work is now measurable:

1. close or correct the 72 partial and 79 missing parent rows;
2. implement and assess the remaining 398 direct clause fixtures;
3. correct the 15 successor-derived foundations that are not yet proven strict-target compatible;
4. preserve native Rust/WASM behavior parity and generated contract boundaries;
5. pass runtime, transport, host, integration, production-build, and release evidence gates before making a compatibility claim.

Authority and validation

The machine authorities are:

• spec-processing/source-manifests/wap-1.2.1-release.json
• spec-processing/source-manifests/wap-1.2.1-effective-spec.json
• spec-processing/source-manifests/wap-1.2.1-class-conformance.json
• the nine wap-1.2.1-*-scr.json family ledgers
• spec-processing/source-manifests/wap-1.2.1-selected-normative-clauses.json
• spec-processing/source-manifests/wap-1.2.1-successor-delta.json
• docs/waves/wap-1.2.1-compliance-program.json

Run the planning gate with:

node spec-processing/scripts/check-wap-release-manifest.mjs
node spec-processing/scripts/check-wap-ingestion-status.mjs
node spec-processing/scripts/check-wap-effective-spec.mjs
node spec-processing/scripts/check-wap-class-conformance.mjs
node scripts/check-wap-external-dependencies.mjs
node spec-processing/scripts/check-wap-external-ingestion-status.mjs
node scripts/check-wap-conformance-ledger.mjs
node scripts/check-wap-selected-normative-clauses.mjs
node scripts/check-wap-delta-register.mjs
node scripts/check-wap-compliance-program.mjs
node scripts/check-requirement-status-drift.mjs

Human rollups are explanatory. If a rollup conflicts with the machine authorities, fix the rollup and its drift check rather than changing the evidence to match prose.