docs: add product roadmap (Harbor storage + Talus on-chain direction)#4
Open
harrymove-ctrl wants to merge 2 commits into
Open
docs: add product roadmap (Harbor storage + Talus on-chain direction)#4harrymove-ctrl wants to merge 2 commits into
harrymove-ctrl wants to merge 2 commits into
Conversation
Plans the next 0-12 months across six areas — Walrus-memory+Harbor, on-chain/smart-contract architecture, crawling/extraction quality, UI/UX, onboarding, and cross-cutting feature gaps — grounded in the current codebase and aligned to the Talus/acc milestones.
This was referenced Jun 16, 2026
Open
Open
Open
…Namespace, web split, CI scope) Fact-checked file:line/symbol/architecture claims against the codebase: - on-chain reads: getObject only in proof.ts/resources.ts; history.ts raw JSON-RPC, resolve.ts SuiNS lookupName, bcs.ts BCS schemas - CloudflareNamespaceStore.authorizeNamespace at worker.ts:502 (was .authorize :503) - apps/web is split into components/ + lib/ (not only the constellation) - CI runs typecheck+test+build (+ gated deploy.yml), not typecheck+test only
Deploying contextmem with
|
| Latest commit: |
6ed3e78
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c09b84bd.contextmem.pages.dev |
| Branch Preview URL: | https://docs-product-roadmap.contextmem.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/ROADMAP.md— a single, grounded product roadmap covering the next 0-12 months across six areas: Walrus/Harbor storage, smart-contracts/on-chain architecture, crawling/extraction, UI/UX, onboarding, and product completeness. The roadmap is aligned to the Talus/acc grant goal of publishingcontextmem.extract/.recall/.rememberas Nexus DAG tools with on-chain attribution receipts.Why
ContextMEM has no custom on-chain layer today: storage is Tatum-gateway (plaintext, mainnet, Node-only, never in the Worker), "private" namespaces are a D1 token check rather than encryption, and there is zero Move code, zero attribution receipts, and zero Talus/Nexus wiring. The roadmap sets a clear direction and sequences the work to ship the grant demo and harden for public launch.
Structure
Key recommendations
registry+receipt) for typed, composable attribution receipts — the one thing Harbor's Bucket/Seal objects don't provide.@mysten/sealin the Worker early — the key runtime unknown that decides where encryption runs.Docs-only change; no code or behavior is modified.