WikiSkill boundary

Type: agentic-system-analyses/types/agentic-system-boundary.md

Boundary and evidence

This run analyses WikiSkill as a documented system for accumulating execution-derived knowledge and using it to evolve reusable agent skills. Its intended use is an account of the source-native mechanism, not a verification of an implementation or an independent replication of reported gains. The target is in scope because its knowledge maintenance, skill proposal and task execution depend on model calls. The target class is memory/knowledge/context-engineering system; the skill-improvement plane is part of that system, not a separate source.

SRC-1, §3 and Appendix A, describe a loop that includes task inference, trace retention, wiki maintenance, skill proposal, validation gating, skill rollback and outcome logging. The source explicitly connects the retained knowledge to later skill updates:

WikiSkill organizes the agent workspace into three layers: a Raw Layer that stores immutable execution traces, a Wiki Layer that maintains structured knowledge, and a Skill Layer that contains evolving procedural knowledge (Figure 2). --- /home/zby/llm/commonplace/.commonplace/worktrees/wikiskill-65116a9d0de7/kb/agentic-system-analyses/state/AAS-2026-10-15-2608-27454-65116a9d0de7-01/sources/arxiv-2608.27454v1-text.txt

While skill updates can be rolled back, the wiki persists so that future updates can build on accumulated knowledge. --- /home/zby/llm/commonplace/.commonplace/worktrees/wikiskill-65116a9d0de7/kb/agentic-system-analyses/state/AAS-2026-10-15-2608-27454-65116a9d0de7-01/sources/arxiv-2608.27454v1-text.txt

The boundary kind is complete artifact, partial loop: the frozen artifact contains the paper's full extracted text, including algorithm, evaluation descriptions and agent prompts, but supplies no executable repository or inspectable end-to-end execution bundle. No repository tree or shipped entry points were acquired. The paper's described harness is included as design evidence; its implementation is not established. This is not a whole-system implementation coverage claim.

Functional coverage and limits

Surface Inclusion and evidence Limit and conclusion prevented
State production and retention Included as doctrine/design: §2–3.1 describe inference trajectories, immutable raw/, wiki patterns, index, evolution log and skill-impact history. No filesystem artifacts or trace bundle is frozen; immutability and persistence are declared, not verified.
Knowledge maintenance Included as doctrine/design: §3.2.2, Appendix C and Appendix E.2 describe sampled traces, wiki context, pattern editing and maintainer output. No maintainer execution is available; adherence to prompt rules and actual patch application cannot be established.
Skill proposal and admission Included as doctrine/design: §3.2.3–3.2.4, Algorithm 1 and Appendix E.3 describe wiki-guided proposal, validation, rollback and harness-written impact records. Harness code and tool implementations are not part of this capture; parsing, enforcement, failure handling and transactional behavior remain unverified.
Later consumption Included as doctrine/design: §3.2.1 and Appendix E.1 describe active skill injection into task agents; §3.2.3 and E.3 describe later proposer access to retained wiki and history. No model-call records are frozen; actual context construction, isolation and cross-iteration reload behavior cannot be checked.
Evaluation and examples Included as reported operation: §4–5, Appendix A.2 and B–D contain benchmark results, ablations, examples and evaluation methodology. These are author reports, not independently inspectable run evidence or causal experiments in this boundary. Aggregate results do not establish per-run behavior or independent causal attribution.
External dependencies Included only as described interfaces: model backends, task data and scoring, task-specific tools and environments (§2, §4.1, Appendix B and E.1). Their implementations and live services are excluded; their correctness, availability, security and contribution to results cannot be assessed. No host responsibility is inferred from their mention.
Related systems and references Excluded as independent analysis targets; their mentions remain contextual paper content. The capture does not authorize inspecting their repositories or treating the paper's comparisons as independently verified characterizations.

The capture was obtained on 2026-10-15 from the linked arXiv v1 HTML. Its stable capture label is arxiv-2608.27454v1-text-2026-10-15, and its exact-byte SHA-256 is recorded above. The text extraction uses Python's standard-library HTML parser, omits scripts and styles, normalizes whitespace within lines, and retains textual content, including appendices. It is a textual artifact, not an image or layout archive: figure-only details, mathematical rendering fidelity and external linked artifacts are not established by it. The original HTML and abstract landing page were saved during acquisition, but only the registered text capture supplies this run's analytical evidence. Later jobs must use the registered capture, not refresh the live page.

The analysis cutoff is 2026-10-15 and applicability is limited to arXiv:2608.27454v1 as captured, not subsequent versions. The overall evidence tier is doc-grounded. No target code, tests, examples or model services were executed.

Source register

Source ID Kind Identity/location Revision or capture Evidence layer Inspected scope Citation anchors Access gaps and conclusion prevented
SRC-1 capture https://arxiv.org/abs/2608.27454 arxiv-2608.27454v1-text-2026-10-15 doctrine/design; reported operation doctrine/design: abstract, introduction, §2–3, Algorithm 1, Appendix B–C and E; reported operation: introduction's result summary and Appendix A.2, B–D evaluation descriptions. The full text is frozen; uninspected results detail remains available, not an access gap. /home/zby/llm/commonplace/.commonplace/worktrees/wikiskill-65116a9d0de7/kb/agentic-system-analyses/state/AAS-2026-10-15-2608-27454-65116a9d0de7-01/sources/arxiv-2608.27454v1-text.txt; section headings §2 Problem Setup, §3 Methodology, Appendix A Method Details, Appendix C Implementation Details, Appendix E System and Agent Prompts No executable source checkout, raw evaluation records or inspectable full-loop execution artifacts are frozen. Supports declared contracts and attributed results, not verified implementation, observed operation or independent causal attribution. Text extraction cannot support image-only or rendering-dependent conclusions.