Repository navigation
feat: public status page and the business case - #33
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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
/status,GET /api/status): one verdict, database reachability, a real probe of every AI model (cached 5 min), and Cloudinary credits with warnings at 80% and 95% (cached 10 min). The quick checks render at once and the AI section streams in. Failures show a category, never a raw provider error. Verdict rules are pure and unit-tested.docs/BUSINESS.md, README): who pays, why it is hard to copy, why Cloudinary's usage pricing fits, unit economics and a pricing hypothesis, every number tagged actual, estimate or assumption, with an explicit note that nobody has paid yet.docs/ARCHITECTURE.md).Verified