This repository publishes a bounded adoption-readiness layer so outside readers can see what the public specs surface is ready for today, which prerequisites apply, and which use cases remain intentionally deferred.
The machine-readable form lives in ../PUBLIC_ADOPTION_READINESS.json.
- explicit
ready,partial, anddeferredposture for the main public audience profiles - concrete prerequisites for each adoption path instead of vague "start here" prose
- bounded non-goals so public readers do not mistake the specs repo for a hosted runtime or full upstream product export
- a synchronized view across audience paths, capabilities, limitations, release evidence, and stronger-source hierarchy
audience-paths.mdand../PUBLIC_AUDIENCE_PATHS.jsonThese show who should read what first.capability-matrix.mdand../PUBLIC_CAPABILITY_MATRIX.jsonThese show what an outside reader can practically do.limitations-register.mdand../PUBLIC_LIMITATIONS_REGISTER.jsonThese show what is intentionally not being promised.evidence-strength.mdand../PUBLIC_EVIDENCE_STRENGTH_MAP.jsonThese show which public surfaces remain strongest when adoption claims and shortcuts disagree.freshness.mdand../PUBLIC_FRESHNESS_MODEL.jsonThese show when readiness summaries go stale and which release-facing evidence should refresh them.release-evidence.mdand../PUBLIC_RELEASE_METADATA.jsonThese show whether the public readiness posture is still aligned with the current verified release state.
Audience paths answer "where should I start?" and the capability matrix answers "what can I do here?". Adoption readiness answers a different question: "what is this public surface actually ready for right now, under which prerequisites, and where are the hard boundaries?".
That distinction matters for serious OSS review. A public repository can be easy to browse while still being unclear about whether it is ready for external review, integration, contribution, or operational adoption. This layer makes that bounded readiness posture explicit.
This layer applies only to the public specs repository. It does not claim a public hosted validator, a full product runtime, or publication of private N1Hub operating surfaces.