Record completion research site deployment
This commit is contained in:
+10
-5
@@ -1,12 +1,13 @@
|
||||
# Next Work
|
||||
|
||||
last_reviewed: 2026-07-27
|
||||
last_reviewed: 2026-07-28
|
||||
|
||||
## P0: Challenge the Completion Research
|
||||
|
||||
The immediate work is not an Agent experiment and not a new evaluation page. Review
|
||||
`research/completion-verification/findings.md` with the user and determine whether its problem
|
||||
decomposition is actually useful.
|
||||
The immediate work is not an Agent experiment or a product redesign. Review the document at
|
||||
`https://agent-eval.k1412.top/` with the user and determine whether the problem decomposition is
|
||||
actually useful. The Markdown sources remain
|
||||
`research/completion-verification/findings.md` and `evidence-ledger.md`.
|
||||
|
||||
The review should test whether the research can answer, without falling back to paper titles:
|
||||
|
||||
@@ -24,6 +25,10 @@ does not prove.
|
||||
Only after this review should the candidate completion certificate, failure object, and recovery router
|
||||
be translated into task contracts. They are currently system inferences, not validated implementations.
|
||||
|
||||
The old v1 evaluation explanation remains available at
|
||||
`https://agent-eval.k1412.top/evaluation-v1.html`. Use it only to compare the premature contract-first
|
||||
route with the current evidence-first research, not as a benchmark result.
|
||||
|
||||
## P1: Prove the Paper Compiler
|
||||
|
||||
The main project goal is now a high-efficiency knowledge funnel, not a paper browser and not a fixed
|
||||
@@ -222,7 +227,7 @@ Still missing:
|
||||
|
||||
For the knowledge-base repository:
|
||||
|
||||
1. read `research/completion-verification/findings.md` with the user;
|
||||
1. read `https://agent-eval.k1412.top/` with the user;
|
||||
2. collect objections, ambiguous terms and missing counterexamples;
|
||||
3. tighten or reject conclusions against the evidence ledger;
|
||||
4. only then convert the accepted model into a minimal task-contract schema;
|
||||
|
||||
Reference in New Issue
Block a user