Preserve initial frontend pattern language research scaffold

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9

sequences/CollaborativeApplication.md

@@ -0,0 +1,15 @@
+# CollaborativeApplication
+
+Status: research stub
+
+A generative sequence for multi-user concurrent interaction, presence, synchronization and conflict resolution.
+
+## Research tasks
+
+- identify dominant forces,
+- establish authority assumptions,
+- determine suitable projection patterns,
+- determine synchronization model,
+- identify failure modes,
+- derive candidate sequence,
+- test against known implementations.

sequences/ContentSite.md

@@ -0,0 +1,15 @@
+# ContentSite
+
+Status: research stub
+
+A generative sequence optimized for content-oriented sites with strong addressability, delivery and progressive-enhancement requirements.
+
+## Research tasks
+
+- identify dominant forces,
+- establish authority assumptions,
+- determine suitable projection patterns,
+- determine synchronization model,
+- identify failure modes,
+- derive candidate sequence,
+- test against known implementations.

sequences/GeneralWebApplication.md

@@ -0,0 +1,112 @@
+# General Web Application — Generative Sequence
+
+Status: hypothesis
+
+## Starting question
+
+How should a web application progressively resolve its frontend architecture without starting from a framework choice?
+
+## Sequence
+
+### 1. Characterize the experience
+
+Identify:
+
+- dominant user activities,
+- interaction intensity,
+- continuity requirements,
+- collaboration requirements,
+- offline requirements,
+- addressability requirements,
+- latency sensitivity.
+
+### 2. Place authority
+
+Choose among patterns such as:
+
+- Server Authority
+- Local Authority
+- Replicated Authority
+- Event-Log Authority
+
+### 3. Establish addressability
+
+Determine what must be named, linked, revisited, bookmarked or shared.
+
+Potential patterns:
+
+- URL as Application State
+- Resource Address
+- Hierarchical Route
+
+### 4. Place projection
+
+Determine where perceivable state is derived.
+
+Potential patterns:
+
+- Static Projection
+- Server Projection
+- Client Projection
+- Hybrid Projection
+- Streaming Projection
+
+### 5. Choose the communication window
+
+Determine whether communication is:
+
+- request/response,
+- polling,
+- long-lived,
+- streamed,
+- replicated,
+- peer-to-peer.
+
+### 6. Add local affordances
+
+Identify state that should remain near the user interaction.
+
+Potential patterns:
+
+- Local Interaction State
+- Pending State
+- Immediate Feedback
+- Optimistic Overlay
+
+### 7. Define mutation and reconciliation
+
+Decide:
+
+- command shape,
+- idempotency,
+- conflict handling,
+- invalidation,
+- resynchronization.
+
+### 8. Establish feature boundaries
+
+Determine which domain and interaction capabilities can evolve independently.
+
+### 9. Establish deployment boundaries
+
+Only split independent deployment where the organizational and runtime forces justify it.
+
+### 10. Strengthen quality boundaries
+
+Apply accessibility, failure containment, security, privacy, observability and performance patterns.
+
+### 11. Measure and adapt
+
+Observe runtime behavior and revisit earlier choices when actual forces differ from assumed forces.
+
+## Research status
+
+This sequence must be tested against contrasting architectures:
+
+- content site,
+- CRUD SaaS,
+- real-time dashboard,
+- collaborative editor,
+- e-commerce storefront,
+- local-first application,
+- microfrontend estate.

sequences/LocalFirstApplication.md

@@ -0,0 +1,15 @@
+# LocalFirstApplication
+
+Status: research stub
+
+A generative sequence for applications in which local state remains usable and authoritative interaction continues despite network loss.
+
+## Research tasks
+
+- identify dominant forces,
+- establish authority assumptions,
+- determine suitable projection patterns,
+- determine synchronization model,
+- identify failure modes,
+- derive candidate sequence,
+- test against known implementations.

sequences/README.md

@@ -0,0 +1,23 @@
+# Generative Sequences
+
+A sequence guides architecture construction through an ordered series of pattern decisions.
+
+Sequences are not mandatory reference architectures.
+
+They should explain:
+
+- starting context,
+- major forces,
+- ordering rationale,
+- decision points,
+- applicable patterns,
+- branches,
+- resulting contexts.
+
+Initial sequence candidates:
+
+- `GeneralWebApplication.md`
+- `ContentSite.md`
+- `TransactionalApplication.md`
+- `CollaborativeApplication.md`
+- `LocalFirstApplication.md`

sequences/TransactionalApplication.md

@@ -0,0 +1,15 @@
+# TransactionalApplication
+
+Status: research stub
+
+A generative sequence for applications dominated by forms, workflows, commands, validation and authoritative transactions.
+
+## Research tasks
+
+- identify dominant forces,
+- establish authority assumptions,
+- determine suitable projection patterns,
+- determine synchronization model,
+- identify failure modes,
+- derive candidate sequence,
+- test against known implementations.