From 63e999d452dca31f5f15bcd84811f26555679f2d Mon Sep 17 00:00:00 2001 From: Seongho Bae Date: Wed, 2 Sep 2026 01:56:54 +0900 Subject: [PATCH 1/2] docs(pages): add product documentation hub --- docs/index.html | 66 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 docs/index.html diff --git a/docs/index.html b/docs/index.html new file mode 100644 index 00000000..2cc3bf6b --- /dev/null +++ b/docs/index.html @@ -0,0 +1,66 @@ + + + + + + + ScopeWeave Docs + + + +
+

ScopeWeave

+

Schedule-control WBS planning that works as a standalone static planner and as a Cloud/SaaS workspace over the same planning model.

+ + + +

Publication truth: this documentation hub describes capabilities present on protected develop. Open pull requests and planned migrations are not shipped product evidence until integrated and revalidated.

+ +

Product responsibility

+

ScopeWeave owns schedule-control planning, WBS hierarchy and editing, deterministic schedule analysis, portable project data, and the optional authenticated cloud collaboration layer. Standalone operation remains a product invariant: cloud capabilities must not make local planning depend on a server, database, credential, or model.

+

Protected develop includes the static planner plus a Node/Hono Cloud/SaaS runtime with account, tenant, collaboration, billing/entitlement, audit, search, integration, and observability surfaces. The current protected persistence profile uses Node SQLite; planned PostgreSQL work is not described here as already shipped.

+ +

Start here

+ + +

Architecture at a glance

+

The static browser planner owns the canonical standalone interaction model. cloud-sync.js adds an optional authenticated cloud overlay. The server layer owns cloud HTTP/API composition, authentication, tenancy, current SQLite persistence, billing boundaries, document integration, bounded attachment refresh, and contextual-orchestrator integration. Cross-service systems are consumed through explicit APIs/adapters rather than shared application databases.

+ +

Onboarding

+

For a no-server evaluation, open the planner on this Pages site or serve the repository with a local static HTTP server. For the Cloud/SaaS profile, install the pinned Node dependencies, provide a durable JWT signing secret, run the server, and follow the deployment guide before exposing the service. Integration consumers should start with the API reference and keep tenant and authorization decisions server-owned.

+ +

Verification and release boundary

+

Repository-native unit/API, browser, coverage, fuzz, dependency, OSV, and security workflows plus organization-required protected checks form the integration evidence. Pending, skipped, cancelled, failed, stale, predecessor-head, or model-only evidence is not equivalent to a passing current revision. Published releases remain distinct from active pull-request behavior.

+ +
ScopeWeave is maintained by ContextualWisdomLab. This Pages hub complements the interactive planner rather than replacing it.
+
+ + From bb9a0565bc4b9417fc8834db005ba6d574c871d6 Mon Sep 17 00:00:00 2001 From: Seongho Bae Date: Wed, 2 Sep 2026 01:57:15 +0900 Subject: [PATCH 2/2] ci(pages): publish product documentation hub --- .github/workflows/pages.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/pages.yml b/.github/workflows/pages.yml index 8b0fba65..c8858acb 100644 --- a/.github/workflows/pages.yml +++ b/.github/workflows/pages.yml @@ -30,11 +30,11 @@ jobs: with: enablement: true - - name: Stage runtime files + - name: Stage runtime and documentation files run: | mkdir -p _site/docs cp index.html 404.html app.js cloud-sync.js analytics.js styles.css toast-state.css wbs.json _site/ - cp docs/user-guide.md _site/docs/ + cp docs/index.html docs/user-guide.md docs/api.md docs/deploy.md docs/security.md _site/docs/ - name: Upload static artifact uses: actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9