Voice + consistency: vary stock formulas, vendor-balance orient.py, unify loop (#48,#49,#51) (#68)
Co-authored-by: claude <claude@jpaul.io> Co-committed-by: claude <claude@jpaul.io>
This commit was merged in pull request #68.
This commit is contained in:
@@ -201,9 +201,9 @@ that same AI hands beyond the repo. The next three modules build directly on it:
|
||||
|
||||
## The AI angle
|
||||
|
||||
A generic integration course would teach you to wire systems together for *programs* to use —
|
||||
fixed clients calling fixed endpoints. MCP is shaped for a different consumer: **an AI that decides
|
||||
at runtime what it needs.** That changes what matters about the integration.
|
||||
Most integration work wires systems together for *programs* to use — fixed clients calling fixed
|
||||
endpoints. MCP is shaped for a different consumer: **an AI that decides at runtime what it needs.**
|
||||
That changes what matters about the integration.
|
||||
|
||||
- **Discovery, not hardcoding.** A traditional client is written against specific API calls by a
|
||||
human. An MCP client hands the AI a *menu* — tool names, descriptions, argument schemas — and the
|
||||
|
||||
Reference in New Issue
Block a user