Skip to content

docs: align with FTW product vision and ownership - #67

Merged
frahlg merged 1 commit into
mainfrom
docs/product-vision-20260912
Sep 12, 2026
Merged

frahlg merged 1 commit into
mainfrom
docs/product-vision-20260912

Conversation

@frahlg

@frahlg frahlg commented Sep 12, 2026

Copy link
Copy Markdown
Member

Align the web client with the shared FTW product vision: clear live intent and outcomes, simple charging, useful expert access and structured agent access through Core. Update the project guide, README, architecture and protocol notes, and add the Sourceful-only PR policy with external issues as the contribution route.

The protocol additions describe targets; they introduce no operation, scope or credential. Distinguish an authorized cloud agent endpoint from the blind relay and escrow. Keep future MCP/LAN work separate from available features.

Validation: npm run verify passed (1,027 tests passed, one skipped; type check and production build passed). README claim checks passed again after the final wording change. New local links and git diff --check passed. No rendered app UI or wire contract changes.

Coordinated product direction: srcfl/ftw#1213. Merge the canonical Core vision before this change.

Coordinated changes: srcfl/ftw#1213, srcfl/ftw-app#2, srcfl/device-drivers#113, srcfl/ftw-web#10.

Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs
ftw-webapp 4809639 Commit Preview URL

Branch Preview URL
Sep 12 2026, 08:50 AM

@cursor

cursor Bot commented Sep 12, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_47f0b9f3-64a3-42bd-8488-caa36b9a91fc)

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 12, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-12T08:54:06.381709Z 4809639 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4809639889

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread README.md
Not yet built: push notifications, the LAN carrier, sharing beyond two roles,
multi-site. Each is listed with its reason in the architecture doc rather than
left implied.
Not yet built: cloud MCP agent access and the WebRTC LAN carrier. The vision

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep multi-site in the unbuilt feature list

For households with more than one paired box, this revised status now implies that only MCP and WebRTC remain unbuilt, but the app still has no normal home switcher: Pair.svelte reduces pairedSites() to sites[0], and currentSiteId() uses the same first-site fallback. The recovery format is only future-proofed for multiple homes and explicitly says “Multi-site is coming.” Retain multi-site in this list, or clearly mark the list as non-exhaustive, so users do not infer that managing multiple homes is available.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant