tegwick
f273a190f0
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
75 lines
4.5 KiB
Markdown
75 lines
4.5 KiB
Markdown
# Research
|
|
|
|
Research material supports the canon but is kept separate from canonical patterns.
|
|
|
|
The structure follows the C3 research deliverable model where useful:
|
|
|
|
- `catalog/` — normalized inventories and indices.
|
|
- `compendium/` — explanatory synthesis of established knowledge.
|
|
- `concepts/` — emerging models and hypotheses.
|
|
|
|
Additional directories:
|
|
|
|
- `cases/` — focused analysis of articles, systems or architectural schools.
|
|
- `plan/` — research program, methods and open questions.
|
|
|
|
Research material may be provisional.
|
|
|
|
Promotion into the canon should happen only after the concept has been reconciled with competing models and tested against multiple frontend architectures.
|
|
|
|
|
|
## Start a research session
|
|
|
|
1. Read [ResearchProgram](plan/ResearchProgram.md) for phases and current work records.
|
|
2. Follow [ResearchProtocol](plan/ResearchProtocol.md) for evidence and promotion.
|
|
3. Select a question from [OpenQuestions](plan/OpenQuestions.md) and a bounded task.
|
|
4. Use [ValidationCases](plan/ValidationCases.md) and the templates in `templates/`.
|
|
5. Update catalogs and question outcomes, then commit and sync the workplan status.
|
|
|
|
Execute bounded source investigations with the [research bench](bench/README.md).
|
|
Its checked-in fixture verifies the pipeline and is excluded from research evidence.
|
|
|
|
Current contrast: [VC-01 server-validated editing](walkthroughs/VC01-TransactionalAdministration.md), [VC-02 offline editing](walkthroughs/VC02-OfflineFieldNotes.md), and [cross-case assessment](reviews/VC01-VC02-Comparison.md).
|
|
|
|
Latest implementation evidence: [frontend recovery](reviews/FrontendRecoveryImplementations.md) and [walkthrough correction review](reviews/RecoveryWalkthroughReview.md).
|
|
|
|
Executable evidence: [Matrix SDK recovery experiment](experiments/matrix-recovery/README.md), with a synthetic receiver and explicit limits.
|
|
|
|
Evaluation: [matched presentation pilot](evaluations/language-pilot-01/README.md) completed twelve llm-connect sessions; results inconclusive, human review pending.
|
|
|
|
Pilot follow-up: [submitted review adjudication](evaluations/language-pilot-01/submitted-review-01/adjudication.md) gives 18/24 obligations in both conditions; model-assisted review, not independent human validation.
|
|
|
|
Current follow-up: [shared guidance corrections](reviews/SharedGuidanceRevision.md)
|
|
and [navigation/rendering evidence](reviews/NavigationRenderingEvidence.md), with
|
|
[provisional VC-03](walkthroughs/VC03-ContentPublication.md). Ten developed hypotheses;
|
|
M1 remains open and the broader M2 evidence gate is not satisfied.
|
|
|
|
Latest expansion: [six broader candidates and decision probes](reviews/PatternBreadthExpansion.md)
|
|
cover presentation logic, derived state, feature organization, client activation,
|
|
failure containment and modal focus. Current total: sixteen developed hypotheses;
|
|
previous counts above describe earlier slices. No additional runtime or model runs.
|
|
|
|
Latest execution: [rendering/focus boundary experiment](reviews/BoundaryRecoveryExperiment.md)
|
|
uses pinned React/Radix packages in Chromium. It records seven stable case observations
|
|
and a timing-sensitive nested-dialog failure; no production or accessibility certification.
|
|
|
|
Nested-dialog follow-up: [ownership isolation](reviews/NestedDismissalIsolation.md)
|
|
captures a stale Escape-listener interval in a 48-trial browser/build comparison.
|
|
A partial guard loses input; a complete remedy remains open. Original results retained.
|
|
|
|
Latest bounded mechanism test: [ownership routing](reviews/NestedOwnershipRouting.md)
|
|
meets 24/24 routed assertions versus 20/24 unmodified controls, with explicit scope
|
|
limits. No delay or readiness wait; no production fork or canonical promotion.
|
|
|
|
Latest breadth evidence: [feature versus deployment boundaries](reviews/FeatureDeploymentBoundaries.md)
|
|
compares pinned example sources and adds [provisional VC-06](walkthroughs/VC06-MicrofrontendEstate.md).
|
|
Independent Feature Boundary develops an existing seed; current corpus has seventeen
|
|
hypotheses and four synthetic walkthroughs. No deployment independence was runtime-verified.
|
|
|
|
Latest execution: [feature release lifecycle](reviews/FeatureReleaseExperiment.md)
|
|
records 14/14 expected observations across two browsers. It distinguishes fresh,
|
|
already-loaded and delayed-load sessions, and includes negative failure controls.
|
|
|
|
Latest release follow-up: [activation conflicts and unfinished-work reload](reviews/ActivationConflictsAndReload.md)
|
|
records 21/21 expected observations, including blind-update and unguarded-reload loss
|
|
controls. Original experiments retained; production atomicity/unload limits remain open.
|