IDEA-003 static knowledge site scope v001
Build and deploy a searchable static reading site with all project notes and downloadable archives on Cloudflare without sign-in.
Objective and decision served
Build a readable static HTML interface for the existing knowledge bundle.1 Intended readers are the private team; the user selects provisional Cloudflare hosting without sign-in, all project notes and downloadable archived source files.2345 The deployed content will be accessible without authentication. Deliver a useful first version rather than a framework comparison study.
Deliverables and acceptance criteria
- Reproducible static build from
knowledge/, using MkDocs plus thin Python preprocessing as the proposed implementation. Markdown remains authoritative. Preserve input and archived bytes; generated staging and HTML live outside the bundle. - Clean documentation layout with navigation, search, readable metadata/status, citations, and working links across ideas, research, entities, decisions, original inputs and scope/approval history. Include all knowledge notes; generated inventories may be rendered as navigation. Project tooling, Git internals, runtime state and credentials are outside the published knowledge content.
- Source detail pages link to original URLs and retained downloadable capture files, preserving provenance and limitations. Third-party HTML is served as an inert download rather than executed in the site origin. If Cloudflare cannot enforce safe download handling, package those files as downloadable archives while preserving their original bytes inside. Missing captures remain visibly missing.
- Local preview and documented build/deploy/update commands; deploy the accepted build to a Cloudflare-provided URL using the user's available account. No custom domain required. Deployment is included in this scope, conditional on account access and service constraints.
- Validation report and exact changed-file handoff. Check representative citations, bundle-root and relative links, deployment subpaths, search, downloads, and output inventory against the input bundle. Check archived download bytes against originals. Check deployed navigation/search and at least one download. Test meaningful preprocessing edge cases and run project script checks at the manager checkpoint.
- Independent Astra design judgment on new site/publication rules and final acceptance of substantive tooling through the manager, with routine Sol implementation. No automatic extra review tier.
Included work and exclusions
Included: one static site, build/preprocessing helpers, bounded dependency installation in the project environment, configuration, concise operating instructions, local verification and initial Cloudflare deployment. All notes and archived files refer to the knowledge bundle at the coordinated build checkpoint. Show archived evidence faithfully without presenting capture success as factual verification.
Excluded: editing research conclusions, rewriting original inputs or captures, publishing repository internals, accounts/repositories created without a concrete need, custom domains, payments, authentication, collaborative browser editing, detector integration, analytics, recurring monitoring and scheduled rebuilds. Updates are reproducible manual builds/deployments in this phase; Git-based automation is a later choice.
Evidence, data access, resources and dependencies
Reuse existing archived MkDocs/Eleventy/GitHub Pages evidence.6 Verify current official Cloudflare deployment and asset constraints plus any implementation-critical generator behavior during execution; archive gathered online documentation using the project workflow. Proposed hard bound: at most six newly gathered official documentation URLs, no paid services or model API calls, no new research study. Stop and request an amendment if these bounds prevent delivery. One bounded implementation assignment and one required independent acceptance pass; manager coordinates design and resource routing.
Cloudflare account access is not yet checked. Use supported connected/browser workflows or existing authenticated tooling; never place credentials in the bundle or generated output. No credential purchase or paid plan change. Asset size, total output size, hosting limits and download behavior are unverified. Inventory locally before upload; report any files that cannot be hosted and seek a scope amendment rather than silently omit them or move them to another service.
Open questions and assumptions
Proposed defaults for approval: documentation-style appearance, MkDocs with Python preprocessing, manual updates, Cloudflare-provided URL and no paid plan. These are agent proposals, not previously recorded user decisions. Framework or hosting changes that materially affect outputs, maintenance or costs require a new scope version.
Account availability, chosen Cloudflare deployment product and free-tier feasibility remain execution dependencies. Deployment cannot be marked complete without a live URL and actual checks. If access is unavailable, preserve the verified local build and record deployment as pending. Newly added notes after the coordinated build checkpoint appear only after a subsequent build; no continuous sync is promised.
Authority and dependent impact
Proposed new authority: static build configuration, preprocessing helper and site operation guidance. Exact implementation paths are allocated by the manager before dispatch; this owner retains the idea package only. Inspect README, dependency declarations, existing validation/index helpers and relevant tests for integration; no changes to scope gates, OKF semantics or role policy are proposed. Manager owns shared indexes/logs/Git. Freeze exact changed paths for independent acceptance and checkpoint; validator success alone does not establish semantic acceptance.
Change from previous scope
Initial version. The recorded choices select audience, provisional hosting and content inclusion; they do not retrospectively authorize implementation.
Approval request
Awaiting explicit user approval of v001 in owning chat 01a124a2-2166-7ae1-b0c5-78e25e85c408, then separate manager start authorization. Receipts record the immutable file's SHA-256 separately. Do not edit this scope to record approval.
-
Exact initial proposal. ↩
-
User selected private team. ↩
-
User proposed Cloudflare for now, without sign-in. ↩
-
User selected all project notes after public accessibility was explained. ↩
-
User explicitly included archived source downloads. ↩
-
Existing preliminary recommendation and capture limitations; no prototype or hosting verification yet. ↩