Principles & Operating Discipline
The shift from "fun side project" to "sustainable business" is a vulnerable moment — community attention, personal pride, and reputation all raise the stakes. These principles are the guardrails we hold ourselves to so ambition stays grounded and the project stays honest.
Operating principles
Launch discipline (Oct 2026)
Before we call it live
- HTTP endpoint reachable at mcp.feelyourprotocol.org
- Open to connect — payment is a later milestone, not a launch gate
- Connect docs describe the hosted path only
- Catalogue honestly lists Runnable vs Planned EIPs
- At least one checked without/with MCP proof published
The public page is MCP is live. This checklist stays here.
Founder traps we watch for
The vision was pressure-tested against a set of recurring psychological/strategic traps. Keeping them visible is part of the discipline:
| Trap | The risk |
|---|---|
| Over- / under-promising | Hype beyond checked fundamentals, or playing it so safe the idea doesn't matter. |
| Undervaluing assets | "AI can do everything" fatalism — forgetting the stack + experience aren't replaceable overnight. |
| AI sycophancy | Asking suggestive questions and getting confident confirmation instead of neutral analysis. |
| Forgetting economics / tech | Treating monetization or feasibility as an afterthought. |
| The community trap | Letting token-community tempo dictate the engineering roadmap. |
| Audience identity crisis | Building in the uncanny valley between human-visual and machine-headless — solved by two legs, one engine. |
| Human-in-the-loop assumption | Designing as if every agent has a person who already allowlisted the tool — the two-audiences failure mode. |
| The infinite-AI-leverage illusion | Assuming easy creation means easy maintenance; over-committing as a solo builder. |
| Solution looking for a problem | Building the API first and hunting for users later. |
| Agentic-UX blindspot | Designing for humans when the consumer is an LLM that will silently misuse a bad schema. |
| Automated-debt avalanche | Trusting the AI-managed fork pipeline's happy path until a silent logic error surfaces. |
| Perfect-protocol procrastination | Over-engineering before a single agent has queried the hosted server in the wild. |
| x402 as the product | Payment rails are how agents access the oracle — not the reason to exist. |
These also make good public-thread material — the project documents its own reasoning in the open.
This page is a living checklist; refine as the project teaches us new lessons.
Changelog
Principles Changelog
- v0.82026-10-06The public page records an open server. This checklist stays the internal bar.
- v0.72026-10-05Same rules. Icon notes for the principles; the launch bar is one checklist.
- v0.62026-10-05Launch week is the public page. This checklist stays the internal bar.
- v0.52026-10-01Launch checklist is the open endpoint. x402 stays a later milestone, not a launch gate.
- v0.42026-09-24Agents are customers; watch the human-in-the-loop assumption.
- v0.32026-09-02PoC shipped — added hosted-product, oracle-proof, and launch-checklist principles; x402-as-product trap.
- v0.22026-06-30Initial founder-traps table and operating principles.