Assess actual scope and plan the reference consumption bridge
Assistant: codex Assistant-Model: gpt-6.1-sol Assistant-Session: 01a1045b-933d-7aa1-b2db-104557487a79
This commit is contained in:
parent
07f1f37374
commit
d413f5f8d0
3 changed files with 252 additions and 103 deletions
181
SCOPE.md
181
SCOPE.md
|
|
@ -1,125 +1,100 @@
|
|||
# SCOPE
|
||||
|
||||
Reviewed: 2026-10-04 · Scope: ongoing research and a versioned knowledge base.
|
||||
Reviewed: 2026-10-04 · Capability audit at `07f1f37`.
|
||||
|
||||
## Purpose and deliverable
|
||||
## What this repository delivers
|
||||
|
||||
Develop a framework-independent frontend architecture pattern language for human
|
||||
and agent reference, following [INTENT.md](INTENT.md). Its intended practical
|
||||
outcome is an explainable path from a frontend problem and its forces to compatible
|
||||
patterns and implementation options.
|
||||
This is a versioned Markdown research knowledge base and a qualified frontend
|
||||
architecture reference. Its purpose follows [INTENT.md](INTENT.md): help a reader
|
||||
move from a problem and its forces to explainable pattern choices and implementation
|
||||
questions. That outcome has been demonstrated through authored examples, but improved
|
||||
real-world decisions and complete generativity have not been established.
|
||||
|
||||
The deliverable is a versioned Markdown knowledge base with structured metadata,
|
||||
traceable evidence and transparent revision history. The language evolves through
|
||||
bounded investigations and review gates; it has no final completion date. Completing
|
||||
an experiment or milestone does not establish a mature language.
|
||||
The product is reference material and research tooling. There is no maintained
|
||||
frontend application, framework, online recommendation service or production runtime.
|
||||
Research fixtures exercise bounded mechanisms; they are not implementation recipes.
|
||||
|
||||
## In scope
|
||||
## Capabilities available now
|
||||
|
||||
- `canon/`: responsibilities, forces, scales, relations and the metadata contract,
|
||||
including testing whether the proposed vocabulary explains contrasting cases.
|
||||
- `research/`: identifiable sources, claim-level interpretations, candidate patterns,
|
||||
counterexamples, pinned implementation studies and bounded executable experiments.
|
||||
- `patterns/`: evidence-qualified canonical records when admission is justified;
|
||||
research candidates remain separately identified until then.
|
||||
- `sequences/` and `architectures/`: decision ordering, compatible configurations,
|
||||
alternatives and resulting contexts, exercised through contrasting walkthroughs.
|
||||
- `technologies/`: descriptive mappings from patterns to implementation approaches,
|
||||
including their constraints and limits.
|
||||
- `templates/`, `scripts/` and the infospace-bench adapter: authoring, metadata checks
|
||||
and reproducible research evaluation. Live model execution uses llm-connect.
|
||||
- `research/evolution/` and `history/`: evidence profiles, immutable snapshots,
|
||||
prospective questions and effort, supersession, learning outcomes and dated
|
||||
assessments. Track applicability, trustworthiness, usefulness, coherence,
|
||||
maintainability and learning efficiency separately.
|
||||
| Surface | What a reader or agent can do | Evidence and limit |
|
||||
| --- | --- | --- |
|
||||
| Human entry and two core sequences | Follow shared-record editing or offline-work decisions, alternatives, failure traces and implementation questions | [START.md](START.md), [transactional](sequences/TransactionalApplication.md), [offline](sequences/LocalFirstApplication.md); synthetic VC-01/02 guidance |
|
||||
| Frozen 0.1 candidate reference | Read 17 pinned draft hypotheses (8 core, 9 extensions), 9 conditional proposed relations, classifications and evidence gaps | [Release registry](reference/releases.json), [index](reference/0.1/index.json); not an admitted canonical graph |
|
||||
| Current research corpus | Inspect 18 developed candidate hypotheses with evidence profiles and retained source/runtime reviews | [Evolution report](research/evolution/EvolutionReport.md); the additional live candidate is outside frozen 0.1, no canonical admissions |
|
||||
| Implementation mappings | Locate scoped mechanisms for transactional and offline recovery | [TransactionalRecovery](technologies/TransactionalRecovery.md), [OfflineRecovery](technologies/OfflineRecovery.md); no product supplies a certified complete configuration |
|
||||
| Metadata and publication checks | Validate contract examples, candidate inventory/hashes, classification, evidence locators and immutable release artifacts | `make schema-test evolution-check classification-check reference-check`; checks establish structural traceability, not source truth |
|
||||
| Research bench | Plan and execute bounded source investigations, retain failures, screen structure and explicitly replay compatible cached runs | [Bench adapter](research/bench/README.md); paid inference uses llm-connect and its task authorization/budget, not automatic invocation |
|
||||
| Learning visibility | Read a selected retrospective ledger, prospective protocols, measured/unknown effort, immutable snapshots and comparison readiness | [ComparisonWindows.json](research/evolution/ComparisonWindows.json); 8 prospective cycles in 7 declared groups, none reaches the 3-cycle review trigger |
|
||||
| Deterministic scheduled reporting | Observe retained natural daily, weekly and October 1 monthly reports from activity-core | [Receipt reconciliation](docs/evidence/2026-10-04-loop-reconciliation.json); zero enrolled consumers, dated owner health snapshot, no admitted pattern-editing executor |
|
||||
|
||||
These areas include intended capabilities; directory presence is not evidence that
|
||||
the corresponding capability is implemented or validated.
|
||||
The frozen preview and live research are separate version surfaces. Published candidate
|
||||
prose is read at its corpus revision; release documents and evidence locators are read
|
||||
at the packaging revision. Legitimate new research does not rewrite the old preview.
|
||||
|
||||
## Current capabilities and limits
|
||||
## Evidence limits and unavailable capabilities
|
||||
|
||||
As of 2026-09-28, eighteen developed research candidates remain draft hypotheses;
|
||||
none is canonically admitted. Sources and claim-level reviews, metadata contract
|
||||
checks, an infospace-bench adapter and bounded runtime research fixtures exist.
|
||||
Four walkthroughs are synthetic drafts or provisional studies, not validated
|
||||
architecture recipes. Six further validation cases remain planned.
|
||||
The four walkthroughs (VC-01/02/03/06) are synthetic drafts or provisional studies;
|
||||
six validation cases are planned. The named files under `architectures/` are research
|
||||
stubs, not developed or validated architecture decompositions. General, content and
|
||||
collaborative sequences contain provisional scaffolding beyond the two developed core
|
||||
paths. Vocabulary and catalog names do not constitute additional implemented patterns.
|
||||
|
||||
The frozen development pilot scored 18/24 in each presentation condition after
|
||||
submitted model-review adjudication. It establishes neither a naming benefit nor
|
||||
equivalence; independent human validation and decision-time measurement remain open.
|
||||
The consumed development pilot scored 18/24 in each presentation condition after
|
||||
model-review adjudication. It establishes neither a naming benefit nor equivalence.
|
||||
Independent human scores, fresh-scenario replication and decision-time evidence remain
|
||||
missing. M1/M2 remain revise/defer, and canonical admission is open. Full canonical graph
|
||||
export, held-out retrieval evaluation and real-repository applicability studies retain
|
||||
their recorded prerequisites. Eight disclosed preview navigation cases are development
|
||||
checks; they are not held-out retrieval results.
|
||||
|
||||
Evolution profiles, a baseline, learning ledger, snapshots and a generated report
|
||||
are implemented. Eight prospective cycles (seven effort-accounted) belong to seven different
|
||||
comparison groups: there is no comparable window for a diminishing-returns claim.
|
||||
Evidence types, implementation families and review provenance remain distinct.
|
||||
Static source mechanisms and authored runtime fixtures do not establish complete
|
||||
pattern recurrence, production fitness or independent human confirmation.
|
||||
Full-contract recurrence, production fitness, accessibility conformance, native crash
|
||||
and off-device recovery guarantees are not established by the scoped source studies or
|
||||
authored runtime fixtures. Seven prospective cycles have positive recorded research
|
||||
time; LEARN-0017's time is unknown. A matching group label is not proof of comparability,
|
||||
and there is no basis for a diminishing-returns or plateau claim.
|
||||
|
||||
Canonical admission, M1/M2 acceptance, demonstrated generativity, full graph export,
|
||||
held-out retrieval evaluation remain open. Scoped mechanism mappings are available
|
||||
in the 0.1 preview; full implementation contracts remain unverified.
|
||||
There is research runtime code, but no maintained frontend application or framework
|
||||
is offered as the product. See the [evolution report](research/evolution/EvolutionReport.md)
|
||||
for current counts and evidence limits; [REVIEW.md](REVIEW.md) preserves the initial
|
||||
2026-09-23 review and is not a current capability inventory.
|
||||
The capability entry and hosted-publication preparation exist, but hosted federation
|
||||
registration and eligible consumer integration lack acceptance evidence. The consumer
|
||||
roster is empty; eligible-task coverage and usefulness are unknown. Deterministic
|
||||
collection/reporting is implemented by activity-core, while producer closeout integration,
|
||||
real use plus linked outcomes, delayed-outcome refresh, admitted bounded investigation,
|
||||
authenticated publication and automatic rollback remain incomplete. Reporting schedules
|
||||
are not proof of a closed autonomous improvement loop.
|
||||
|
||||
## Research boundaries and exclusions
|
||||
## Boundaries
|
||||
|
||||
- Do not build or operate a general frontend application, framework, router or
|
||||
release platform as the deliverable. Fixtures exist to investigate claims.
|
||||
- Do not rank frameworks, prescribe a universal architecture or turn the language
|
||||
into a component cookbook or collection of tool-specific idioms.
|
||||
- Do not treat candidate counts, source counts, passing assertions or model agreement
|
||||
as maturity, independent recurrence or proof of usefulness.
|
||||
- Do not infer accessibility conformance, production guarantees or upstream defects
|
||||
from bounded DOM experiments or partial source inspection.
|
||||
- Do not combine viability dimensions into a maturity percentage, infer historical
|
||||
effort from commits, or pool incomparable studies to claim learning saturation.
|
||||
Research covers framework-independent authority, addressability, projection, mutation,
|
||||
recovery, interaction, composition and delivery decisions. Additional coverage must
|
||||
come from useful questions, contrasting contexts and traceable evidence. Authoring,
|
||||
validation and qualified reference improvements are in scope; canonical admission and
|
||||
stronger evidence claims require the existing reviews.
|
||||
|
||||
## Work ownership and review boundaries
|
||||
Do not turn the deliverable into a framework ranking, component cookbook, general
|
||||
frontend runtime or universal architecture prescription. Do not infer maturity from
|
||||
catalog size, fixtures, model agreement or automation definitions. Do not fabricate
|
||||
human ratings, historical effort, consumer use, complete contract recurrence or
|
||||
unsupported guarantees. Policy/access/budget changes in the operating loop remain
|
||||
monthly human decisions; qualified reference work can continue within existing scope.
|
||||
|
||||
[WP-0002](workplans/FEP-WP-0002-seed-language-validation.md) delivered seed evidence and
|
||||
the connected corpus (finished; M1 revise/defer). [WP-0009](workplans/FEP-WP-0009-m1-independent-validation.md)
|
||||
owns independent M1 validation. [WP-0003](workplans/FEP-WP-0003-contrasting-schools.md)
|
||||
owns contrasting streams, broader walkthroughs, ontology decisions and M2.
|
||||
[WP-0004](workplans/FEP-WP-0004-reference-surface.md) is blocked follow-up for graph,
|
||||
held-out retrieval and real-repository applicability, subject to its recorded gates.
|
||||
[WP-0006](workplans/FEP-WP-0006-language-evolution.md) owns ongoing learning visibility,
|
||||
review dates and comparable-cycle measurement. Actionable work stays in workplans;
|
||||
this file describes boundaries, not a second backlog.
|
||||
## Work and assessment ownership
|
||||
|
||||
[WP-0007](workplans/FEP-WP-0007-language-v01-preview.md) packages a finite 0.1 research
|
||||
preview: curated candidate reference paths, two core sequences, scoped mappings and
|
||||
a candidate export. This is a bounded research preview, not a replacement for M1/M2/M3.
|
||||
[WP-0009](workplans/FEP-WP-0009-m1-independent-validation.md) owns the independent M1
|
||||
validation residual of finished WP-0002. [WP-0003](workplans/FEP-WP-0003-contrasting-schools.md)
|
||||
owns architectural contrasts, broader walkthroughs and M2; [WP-0004](workplans/FEP-WP-0004-reference-surface.md)
|
||||
owns gated canonical export, held-out retrieval and real-repository evaluation.
|
||||
[WP-0006](workplans/FEP-WP-0006-language-evolution.md) owns comparable learning evidence;
|
||||
[WP-0008](workplans/FEP-WP-0008-use-driven-improvement.md) owns discovery, eligible
|
||||
consumer integration/outcomes and end-to-end autonomous improvement. Workplan files
|
||||
are authoritative; this document is a capability inventory, not a duplicate backlog.
|
||||
|
||||
The [2026-09-27 scope–intent assessment](history/2026-09-27T010237+0200-scope-vs-intent.md)
|
||||
records the current gaps and recommended priorities. Future assessments should
|
||||
preserve that historical judgment and cite changed evidence.
|
||||
|
||||
## Ecosystem reuse and operational learning
|
||||
|
||||
The user-directed [WP-0008](workplans/FEP-WP-0008-use-driven-improvement.md) connects
|
||||
qualified reference use to evidence-bearing consumer receipts and bounded autonomous
|
||||
improvement. It owns discovery, instrumentation and execution integration; monthly
|
||||
human review owns operating-policy decisions. The capability entry is prepared;
|
||||
automatic collection and three activity-core reporting schedules passed scheduled
|
||||
smoke checks; the first natural daily run failed after a worker image change removed
|
||||
the domain resolver. The approved grant-preserving repair is deployed and all three
|
||||
scheduled sink smokes pass. Retained natural daily and weekly runs and the October 1
|
||||
monthly report are now verified against State Hub receipts; that report covers
|
||||
September and carries a dated owner health snapshot. See the
|
||||
[reconciliation evidence](docs/evidence/2026-10-04-loop-reconciliation.json).
|
||||
Hosted consumer integration and admitted pattern-editing execution remain blocked;
|
||||
there are no enrolled consumers yet.
|
||||
This operational loop can improve draft guidance without claiming M1/M2/M3 or
|
||||
independent-human validation. See the [operating design](docs/ReuseAndImprovementLoop.md).
|
||||
The [current scope–intent assessment](history/2026-10-04T084941+0200-scope-vs-intent.md)
|
||||
prioritizes consumer decision/outcome evidence, independent validation and qualified
|
||||
reference consumption over catalog expansion. [WP-0010](workplans/FEP-WP-0010-reference-consumption.md)
|
||||
implements the bounded local consumption bridge; it does not replace empirical owners.
|
||||
The [September 27 assessment](history/2026-09-27T010237+0200-scope-vs-intent.md) remains
|
||||
historical evidence of the earlier judgment.
|
||||
|
||||
## Registration
|
||||
|
||||
- Repository: `frontend-patterns`
|
||||
- Category: `research`
|
||||
- Domain / topic: `infotech / canon`
|
||||
- Workplan prefix: `FEP-WP`
|
||||
|
||||
The topic groups this research with semantic coordination work; it does not imply
|
||||
that the proposed language is an adopted fleet standard.
|
||||
Repository `frontend-patterns` · category `research` · domain/topic `infotech / canon`
|
||||
· workplan prefix `FEP-WP`. Registration does not imply an adopted fleet standard.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue