tegwick
71a8c1424b
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2.8 KiB
2.8 KiB
Forces
Forces make architectural decisions non-trivial.
The initial force vocabulary is intentionally broader than frontend implementation concerns.
Experience
interaction-latency— interaction latencyperceived-responsiveness— perceived responsivenesscontinuity-of-interaction— continuity of interactiondiscoverability— discoverabilityaddressability— addressabilityaccessibility— accessibilityrecoverability— recoverabilityoffline-usability— offline usability
Information
authoritative-consistency— authoritative consistencyfreshness— freshnesscacheability— cacheabilityconflict-probability— conflict probabilitycollaborative-concurrency— collaborative concurrencydata-locality— data localityprivacy— privacyinformation-completeness— information completeness
Execution
first-content-latency— first-content latencyhydration-cost— hydration costclient-compute-cost— client compute costserver-compute-cost— server compute costbandwidth-cost— bandwidth costconnection-lifetime— connection lifetimenetwork-reliability— network reliabilitystartup-cost— startup costincremental-update-cost— incremental update cost
Change
feature-change-frequency— feature change frequencyschema-change-frequency— schema change frequencyindependent-deployability— independent deployabilityteam-autonomy— team autonomyrelease-coupling— release couplingcompatibility-pressure— compatibility pressure
Engineering
implementation-complexity— implementation complexityreconciliation-complexity— reconciliation complexitycognitive-load— cognitive loadtestability— testabilityobservability— observabilitydebuggability— debuggabilityportability— portabilitysecurity-exposure— security exposure
Operations
scalability— scalabilityfault-containment— fault containmentdeployment-complexity— deployment complexitycache-invalidation-complexity— cache invalidation complexitytelemetry-quality— telemetry qualityincident-recoverability— incident recoverability
Research questions
The vocabulary should remain small enough to reason with.
Research should determine:
- which forces are independent,
- which are merely metrics,
- which are compound concepts,
- which forces recur across most frontend patterns,
- which forces should be modeled as dimensions rather than labels.
Force IDs above are stable kebab-case keys. Improvements/worsenings describe favorable/unfavorable effects, not a numerical increase/decrease in a metric. Aliases or renames must preserve existing references; add vocabulary entries before use.