DJP 3cb1973f57 Fix tier matching: use client tier to pick correct complexity variant ... - Doc parser now extracts tier labels (Tier A, A, Gold, etc.) per asset - Matching uses tier to find the correct GMAL complexity variant: - Claude matches to the GMAL family (asset type) - Post-match lookup: (asset_name + target_complexity_level) finds exact variant - e.g. "Banner - Tier A" with A=Complex → finds Complex variant by asset_name query - Tier hint passed to Claude prompt for better matching - No blind expansion - only the tier-appropriate GMAL is matched - Expand to Tiers button still available for when client doesn't specify tiers Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-04-09 15:17:20 -04:00
..
__init__.py	Initial commit - GMAL Scope Builder	2026-03-27 17:35:14 -04:00
deps.py	Initial commit - GMAL Scope Builder	2026-03-27 17:35:14 -04:00
efficiency.py	Remove Cortex from tool presets	2026-04-09 14:39:19 -04:00
gmal.py	Client tier mapping + GMAL complexity variant expansion	2026-04-09 15:02:45 -04:00
ingest.py	Initial commit - GMAL Scope Builder	2026-03-27 17:35:14 -04:00
matching.py	Fix tier matching: use client tier to pick correct complexity variant	2026-04-09 15:17:20 -04:00
projects.py	Client tier mapping + GMAL complexity variant expansion	2026-04-09 15:02:45 -04:00
ratecard.py	P1: Role-specific efficiency profiles + BTG tool efficiencies	2026-04-09 13:48:30 -04:00