diff --git a/agent-ops/factory-agent-ops/SKILL.md b/agent-ops/factory-agent-ops/SKILL.md index 73da501..e1b05d4 100644 --- a/agent-ops/factory-agent-ops/SKILL.md +++ b/agent-ops/factory-agent-ops/SKILL.md @@ -3,8 +3,8 @@ name: factory-agent-ops description: Act as a project's lead for ideas, research, accepted tasks or an approved backlog; coordinate native workers, independent review and authorized delivery. license: MIT metadata: - version: "0.1.13" - updated: "2026-10-12" + version: "0.1.14" + updated: "2026-10-15" --- # Factory Agent Ops @@ -61,11 +61,18 @@ authorized check output. Read their evidence and resolve findings; a successful tool call or finished turn does not establish acceptance. Recheck affected evidence after fixes, rebases or changed scope. -Before bringing work to a person, ensure the implementer supplied a short, -current handoff showing the change and useful proof, with detailed records linked. -Point out the few review targets, your recommendation and the actual remaining -decision. Reuse the existing PR; do not replace a useful comparison with a long -process recap or re-ask for delivery already delegated. +Write issue openings, progress updates and final handoffs for the person reading +them. Lead with the useful point in plain words, understandable without the chat +or opening links. Use a real example when it clarifies the change, such as an +actual before/after excerpt or result; use real images when they show a visible +change better. Keep a failure +or missing check that affects the decision visible. Put sources, logs and detailed +proof behind a few optional links or collapsed details; exact operator commands or +identifiers belong below the summary, not in its place. Before bringing a candidate +to a person, ensure the implementer's current handoff does the same, then point out +the few review targets, your recommendation and the actual remaining decision. +Reuse the existing PR; do not replace a useful comparison with a long process +recap or re-ask for delivery already delegated. Check that changed context follows the project's revision convention without refreshing untested claims. Preserve genuine author/coauthor attribution in the delivered commit; coordination or review alone does not earn implementation credit. diff --git a/docs/qualification.md b/docs/qualification.md index 2e57cdc..bbed35d 100644 --- a/docs/qualification.md +++ b/docs/qualification.md @@ -11,6 +11,7 @@ remain with the installation; public issues track the remaining acceptance work. | --- | --- | --- | | Package | Eight portable skills, metadata/link checks and staging tests | Mechanical checks do not establish agent decisions | | Foundation readiness handoff (0.1.12 candidate) | 2026-10-11: [Factory #27](https://github.com/arcitai/factory/issues/27) source change after an AIOS assessment accepted a stale mandatory authoring self-dependency, its disabled private reporting was found only by readback, its lead could not read its private record, and Project1's current README kept stale pre-delivery claims (coordinator observations, not reproduced here). Package, unit and staging checks only | Behavioral evidence and independent review are pending in the delivery PR. Native binding/authentication behavior stays with [Factory #3](https://github.com/arcitai/factory/issues/3); Markdown does not repair it | +| Human-facing updates (0.1.14 candidate) | 2026-10-15: [Factory #36](https://github.com/arcitai/factory/issues/36) after the lead's [#35 comment](https://github.com/arcitai/factory/issues/35#issuecomment-6193954207) opened with a native version line, a five-row terminology table and long source paragraphs. The same comment was rewritten and read back to open with the finding in plain words and one before/after of the guide, with checks and the freshness limit visible and sources in optional details. AgentOps source clarified for issue openings, progress updates and final handoffs | One authored issue revision, not a comprehension measurement, future agent reliability, native permission or app UI change. Source checks and independent review are recorded in the delivery PR | | Usage readiness (0.1.14 candidate) | 2026-10-15: [Factory #35](https://github.com/arcitai/factory/issues/35) source assessment of T3 upstream `d83929ad` usage docs, usage contract and environment-auth guidance (lead research, not reproduced here). The lead observed a native identity readback of the execution host's running server. The existing Mac operator then observed Usage in native Nightly 3010 (`d83929ad0bb0`) with one environment (selecting it still reads All environments): Cost, Tokens and Limits; 24 h/7 d/30 d/90 d history; Codex/Claude Code provider menu; Model or Day breakdown; no project, thread or account filter; Cost labeled an API estimate with unpriced usage itemized; Tokens as input, cache read, cache write and output; Limits showing account reset windows with history-period controls disabled. No refresh, reset, setting, account or billing change; the original view was restored | Limits showed no stale/unknown/error marker but no unambiguous as-of time, so quota freshness is not established. No project accounting, per-project quota, OS isolation or host adoption proof; upstream project attribution was unmerged at the 2026-10-15 readback. Package/unit/staging checks and independent review are tracked in the delivery PR | | Review check artifacts (0.1.13 candidate) | 2026-10-12: source change after an application operator reported (not reproduced here) that an OpenPaperDesign reviewer was told to modify no files yet asked to compile/test; Rust targets filled the shared `/tmp` quota, automatic approval refused cleanup under that instruction and the reviewer held without bypass. The operator later removed only an earlier completed task's rebuildable target after checking no process used it. Package, unit and staging checks only | Behavioral evidence for source-only, authorized-check-output and shared/active-artifact cases and independent review are recorded in the delivery PR. Project scratch setup stays with that project | | Persistent choices (0.1.10 candidate) | 2026-10-10: a fresh native Astra xhigh context answered four textual cases against `7f846946`: hypothetical settings stayed unauthorized; external read access retained scope and removal; provider-wide controls did not become project isolation; uncertain application, upgrade drift and expired exceptions required reconciliation | Method rehearsal, not live grant/revocation or a reliability measurement. Independent review of the combined source/presentation is tracked in the delivery PR |