Factory 0.1.17 — Verify progress after a blocked request

AgentOps follows blocked work through to useful progress instead of treating a handoff or queued correction as recovery. The guide uses an observed OPD recovery to explain real Decline/Cancel semantics and safe continuation.

Package checks, 11 tests, staging, independent review and required CI passed. Native wake, scoped approval authority and worker isolation remain open in #32; this release changes guidance only.

Factory 0.1.16: prepare inputs before delegation

Prepare accepted inputs before delegating text work, use native file tools, and assign checks and artifacts explicitly. Existing permissions and refused calls stay intact.

One Factory Opus task read prepared inputs and made the expected edit without a shell command or approval card. Package checks, 11 unit tests, staging, independent Sol Max review and required PR/main CI passed.

This is a bounded method improvement. No notification hook, approval responder, runtime or worker-isolation layer is installed. Remaining native gaps stay open in #32.

Delivered in #41. Recovery: retain the prior reviewed v0.1.15 skills and preserve local adaptations before adoption.

Factory v0.1.15

Factory deliverables now default to English. Issues, PRs and Factory documentation use another language only when the user explicitly requests it; the language of brainstorming does not select the deliverable language.

Delivered through PR #40, with independent exact-candidate source acceptance, passing required PR/main checks, the package check, 11 unit tests and bundle staging. The authored issue corrections are bounded examples, not a claim of future autonomous compliance.

This is a method-only source release. Native runtime, permissions and isolation qualifications are unchanged. Review the skill diff before adopting; retain the previous installed copy for recovery.

Factory 0.1.14

Factory 0.1.14 clarifies native T3 usage and makes issues and progress updates easier to read.

• Foundation explains the Cost, Tokens and Limits views, including API estimates versus actual billing and subscription limits. Projects and environments are distinguished: the observed native view does not provide project accounting.
• AgentOps applies its existing plain-language handoff guidance to issue openings and progress updates. Examples and real images are used when they help; detailed evidence stays available behind the useful explanation.

The native Usage view was observed in the installed T3 Nightly 3010 Mac client. Its independent data freshness and project attribution remain unqualified. The issue-writing evidence is one actual revision and rendering, not a future reliability or comprehension result.

Verification: eight skills checked, 11 unit tests passed, staged Foundation and AgentOps bytes verified, separate independent source reviews accepted, and PR/main Method checks passed. Native approval authority, worker isolation and daily host updates are unchanged.

Changes: PR #37, PR #38. Follow-up: usage coverage #35, human-readable updates #36.

This release supplies source and skill bundles; installing it is a separate verified adoption. Recovery uses the previous reviewed v0.1.13 and preserved local installed bytes.

Factory 0.1.13 — clear scope for review checks

Factory 0.1.13 clarifies reviews that need builds, tests or staging: AgentOps specifies permitted generated outputs and scratch space; Review keeps product sources unchanged and holds shared, active or unauthorized cleanup.

Independent review passed. Both affected bundles staged successfully with unchanged source hashes; PR and main CI passed. No permissions, model defaults, runtime or Foundation requirements change.

See PR #29 for the three behavioral cases and their limits. This release does not establish unattended operation.

For adoption, stage and compare the changed AgentOps and Review skills against each selected installation, preserve local adaptations and reload the sources explicitly. The previous reviewed release, v0.1.12, remains the recovery source.

Factory v0.1.12

Factory v0.1.12 clarifies the existing Foundation readiness and handoff method.

Foundation now makes the final evidence/consistency pass explicit across relevant project instructions, dependency and distribution assumptions, selected remote controls and maintenance records. Readiness holds only dependent capabilities when prerequisites contradict the evidence. Documented bootstrapping remains valid; small repositories can keep existing sources and justified not-needed controls.

The private reporting guidance requires actual readback when GitHub private reporting is the chosen route; SECURITY.md alone is not activation proof. An inaccessible adoption record names its real maintainer and access limit. Reassessment reuses records, preserves historical proof dates and corrects stale current claims.

Implementation and independent source review: PR #28, addressing #27. Reviewed head c45286c; release commit 078b684 has the identical tree 8c61e4b5d01c093617aaa37b881a4edaa665db02. Human author and the genuine Claude Opus 5.5 coauthor are retained in the merged commit history.

Verification: writer and fresh independent reviewer each passed the package checker (8 skills / 0 errors), 11 unit tests and whitespace checks. Disposable Foundation staging bytes matched the candidate. Six positive/negative textual decision scenarios passed independent review. PR CI and main CI passed on their exact commits.

These scenarios are source exercises, not new live setup, automatic instruction-loading or unattended-operation proof. The writer needed three individual operator approvals; an incidental read refusal and a corrected reporting error remain in the PR evidence. No permissions, models, native settings, runtime or optional application stack changed. Native operator qualification remains separate in #3.

Install/adopt only the reviewed skill bundle after comparing existing local adaptations. Publication does not reload native skill bodies or prove installation; explicit adoption/readback remains separate. For recovery, retain the previous reviewed v0.1.11 bundle and preserve private native state/local adaptations.

Factory 0.1.11 — verified writer recovery

AgentOps now explains how to recover a writer into a clean, newer worktree while preserving its task changes, upstream content and actual provider-native identity.

• Stop for drift, preserve the original evidence, and confirm the accepted target before integration.
• Use the supported T3 client/worktree route and verify native identity; a matching conversation title or ID is insufficient.
• Keep an explicit handoff decision when required continuity cannot be established.

The linked AIOS replay passed independent review, including conflict, provenance, authority and failed-check cases. It is operator-assisted proof on one pinned T3/Codex setup, not a guarantee of autonomous recovery, automatic instruction loading or support across every harness.

This method-only update changes two installed AgentOps source files. It adds no runtime, permission or model setting. Final CI passed the package checks and 11 unit tests; independent native source review passed. The reviewer’s own unit-test attempt was blocked by its read-only temporary-directory policy and was not retried with wider access. Installed adoption is a separate readback.

Changes: #26

Factory 0.1.10

Factory now gives lasting project settings a clear upkeep owner: Foundation establishes the existing configuration/adoption record, and that project’s AgentOps maintains it.

• Record meaningful model, skill, tool, update, connection and access choices, with their actual scope, source, authority and removal/recovery path.
• Distinguish intended, applied and verified settings. Hypothetical examples do not grant access.
• Clarify native writer/worktree binding and one AgentOps per application project.
• Refresh the README and Arc’ It AI banner, preserving upstream branding and font terms.

Validation: 8-skill checks, 11 tests, portable bundles, four textual decision cases, a routing case and independent native T3 review. The review’s branding finding was corrected and the revised source passed follow-up. No configuration engine, new permission, account connection or global model change is added. Source delivery and installed/native adoption are separate observations.

Changes: #25

Factory v0.1.9 — portable engineering Foundation

Factory Foundation now includes the engineering preparation previously maintained in AIOS: reproducible setup, maintained project documentation, design and interface continuity, and actual instruction-loading checks.

The optional three-hour CI/CD profile is preserved, including exact-revision evidence, retries, failure handling and preview/recovery requirements. Existing healthy full-per-PR pipelines remain valid. This release enables no schedule or deployment.

PR #24 contains the source mapping, independent review and three textual instruction cases. Package checks (8 skills), 11 tests, disposable staging, PR CI and merged-main CI passed. Merge tree matches the reviewed candidate. AIOS removes its duplicate skill in a separate release.

Native automatic instruction loading, application deployment and installed adoption require their own proof; this source release does not establish them. The prior v0.1.8 release remains available for recovery.

Factory v0.1.8 — scoped Foundation readiness and mobile qualification

Foundation now distinguishes the execution host from the application repository and hands AgentOps one short readiness result: verified capability, required gap, or justified conditional choice. It reuses relevant host evidence and the project's existing records; no extra skill, runtime or documentation collection is introduced.

Dated qualification now includes a real background iPhone question/answer, mobile-data use, a closed lid on external power and desktop logout. These qualify the observed paths only. Host-network outage, battery/suspend recovery and every approval type remain untested.

Validation: independent candidate review and two textual behavioral rehearsals passed; 8 skills checked, 11 tests passed, and merged-source CI is green. See PR22.

Adoption: review the changed Foundation bundle before copying it into a selected harness scope. Publication alone does not update an installation. Preserve local adaptations and use v0.1.7 as the previous reviewed recovery source.