docs(learn): describe learn's real deployment, not the estate Cloud product - #35
Merged
Merged
Conversation
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
1 participant
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.
learn/docs/deployment.md framed learn.cogitave.com as a metered surface behind the cogitave-cloud gateway, with membership + a 25-request free-tier fence. That is wrong - learn is a free, public Cloudflare Pages site and its MCP is a direct edge Function (functions/mcp.js): no gateway, no auth, no fence, no metering. Those belong to the managed Cloud product (governed Core at mcp.cogitave.com), a separate surface. This rewrites the doc to describe learn's actual deployment and only link out to the Cloud product; also drops the stale 'nothing is deployed' framing (learn is live). Internal doc (not published), so no user-facing change.