t2000-engineering

t2000 Engineering Discipline

Merged 2026-07-24 from four Cursor rules that were alwaysApply: true (engineering-principles, goal-driven-execution, coding-discipline, product-build-algorithm). The load-bearing assertions live in CLAUDE.md § Engineering Discipline and apply every turn; this file is the depth behind them.

---

1. Trace the full path BEFORE writing code

Before fixing any bug, trace the ACTUAL execution path from user action → API route → handler → SDK → on-chain → response → UI render. Verify which functions/routes/ handlers are actually called. Never assume.

What went wrong once: spent 4 iterations fixing sdk.swap() balance-change parsing when the Audric web app uses a sponsored transaction flow (/api/transactions/prepare → sign → /api/transactions/execute) that never calls sdk.swap() directly. The fix needed to be in the client-side handleExecuteAction, not the SDK.

Checklist before implementing a fix:

1. What is the ACTUAL data flow? (trace it, don't guess)
2. Where does the data first become wrong? (that's where to fix)
3. Does this fix introduce duplication? (if yes, rethink)
4. Will this fix survive adding a new token/asset/feature? (if no, rethink)

2. Single source of truth — never duplicate

If data exists in one place, import it. Never copy token maps, decimal maps, or config into multiple files.

// ❌ BAD — hardcoded list that gets stale
const COMMON_TOKENS = 'SUI, USDC, USDT, USDSUI';

// ✅ GOOD — derived from canonical source
const { TOKEN_MAP } = await import('@t2000/sdk');
const supportedTokens = Object.keys(TOKEN_MAP).join(', ');

Live product is the same rule. PRODUCT.md is the one-page map of what we sell. Passport plan SKUs live in audric/packages/accounts/src/tiers.ts (+ featured-cap.ts for pin caps). Job bounds / escrow bps live in SDK constants + Move. Do not write those tables from memory, and do not invent a second catalog (FEATURE_INVENTORY.md, a revival of SITE_REPOSITIONING_BRIEF.md). Kill a sold perk in audric → patch t2000 PRODUCT.md the same day.