Find every platform capability
Choose the right SDK, workflow and operating surface from one capability map.
Farther Shore supplies the identity, entitlement, commerce, hosting and operating layer around your application. Your application owns its product behavior and data. Start with the customer's task, choose the platform capabilities it needs, and follow the owning surface below.
Choose the owning surface
| Task | Read first | Execution surface |
|---|---|---|
| Define routes, grants, plans, pricing and bounds | Business program | TypeScript in business/ |
| Verify callers and report measurements | Backend metering | Backend SDK |
| Build a custom customer application | Frontend overview | Frontend SDK |
| Understand a bill, balance or subscription pin | Commerce guide | Billing reference and CLI reads |
| Explain a denied request | Gateway guide | Denial evidence and signed context |
| Publish, recover, manage customers or secrets | Operations guide | CLI and Git |
| Work with governed agents and automations | Agent guide | Explicit agent tools and handoffs |
| Find an exact command or tool schema | CLI and MCP guide | Generated command and tool references |
Read with an agent
Fetch the machine index, then the collection relevant to your task. The complete corpus contains all visible page source. The capability catalog records package versions, exact public exports, commands, tools, permissions and handoff reasons. The corpus includes MDX: preserve code fences and read callout content rather than treating the file as executable code.
Each reference is tied to the workspace packages used to generate it. Compare that version with your application's package pin and the installed CLI. A locally installed CLI can lag the docs. Use the pinned package contract and current command help; do not combine examples from incompatible majors.
Learn the connected system
Read ownership, identity, economics versus entitlements, and release pins before composing a product. These explain why an authorized member can still hit a plan bound, why a frontend permission gate cannot protect backend data, and why publishing a new price does not silently reprice every subscriber.
For each change, record the business and environment, choose its owner, perform the documented workflow, then verify the resulting state. An accepted write, completed apply, healthy backend and settled bill are different observations.