AOCI-CODE v0.2.0-rc1预发布2026-11-05
AOCI-CODE v0.2.0-rc1 is built from 91e3936ff65b77e8166ae83efdeacf2a7b00a193.
The first 0.2.0 candidate: the speed work, the one-call closing, and
host-dialog approval, with the Legacy single-file write path retired. An entry
that changes a persisted preimage names the binary every machine then needs.
Upgrading from 0.1.x:
- A Legacy single-file index, an aoci.txt that carries its own Header and
Entries, is read-only apart from a Managed Scope transaction;
aoci cognition onboard migrates it.
- A tracked module named logs or run becomes a Missing Entry, because
neither name is a built-in exclusion any more.
- The aoci baseline scope commands are gone; aoci scope covers them. A
baseline scope transaction 0.1.x left pending is resumed with 0.1.x
before the upgrade; this release reads its intent as an invalid scope
receipt, which blocks the repository until it is moved out of
.aoci/transactions.
- A repository initialized by this release uses sensitivenamerules v2 and
may declare a SQLite source. A 0.1.x binary answers such a repository with
scopechangerequired or refuses the declaration, so every machine that
maintains it needs this release.
Changes:
- The Whole-Index maximum no longer refuses anything. An index may be read
outside an Agent's context window, so its total size only names the budget
status (healthy, near_budget, warning, exceeded): an Entry Apply, a
Scope Change, check, the Guide, and cognition_optimization no longer
stop when the Whole-Index passes max_tokens, and scope status no longer
reports cognitioncompressionrequired. In enforce mode the R and S limits
still return an Entry over its limit to the model, and the Guide and
next_commands for that stop now name the band
(scope budget set --policy-file {policy_file}) instead of --max-tokens.
No configuration or Baseline byte changes, so no repository needs a Scope
Change; a 0.1.x binary still enforces the maximum on the same configuration.
- After a merge, a Code or Database Volume whose bytes no longer match the
Baseline is restored together with the Root, every other Volume, and
.aoci/baseline.json from one commit. The repair action of
codevolumeunbaselined and databasevolumeunbaselined used to say
"restore them": restoring a Code Volume alone matched its own Baseline
record while the Baseline still bound the other branch's sources, so an
Entry that branch had re-authored went back to its older text and Maintain
reported the repository aligned. Restored as one set, Maintain returns every
source or table the restored Entries do not describe, after any Scope
Change, Locale switch, or Observe review it names first. These two findings
and metavolumebaseline_drift no longer suggest re-establishing cognition
through a Scope Change, because a Scope Change cannot rebaseline a formal
Volume; rootvolumebaseline_drift names it only for the Root an older
Database Bootstrap left, the one Root drift a Scope Change reconciles.
v0.1.x prints the old wording for every Volume; follow this one.
- Every batch of a cognition_optimization pass reports the floored S
maximum. Since #146 only the batch that starts a pass carried an
smaxtokens floored by the Meta's S quota; the current batch delivered
again and every later batch fell back to the machine default, under-reporting
the limit Apply enforces wherever the Meta declares a looser quota. No
identity or batch cut changes.
- aoci config set locale works on a Volumes v1 repository. It used to be
refused once the index existed, so a repository created in one Locale
could not move to the other without being rebuilt. The switch is one
resumable transaction over the Root's #Locale line, the team
configuration, and the Baseline record of the Root; the Meta, Code, and
Database Volumes are guards and keep their bytes, so no Entry is rewritten.
Locale is prospective: existing Entries keep their language, Entries
created or updated afterwards use the new one, and the Maintain contract
says so. A crash leaves locale-<id>.json under .aoci/transactions,
which the same command resumes while every other command waits; a Root
whose #Locale disagrees with the configured locale is the governance
finding rootlocalemismatch, repaired by the same command; an absent
team file takes the Root's explicit marker as the project Locale.
init --locale on an existing Volumes repository points to this command.
Ported from dignfei's Locale-switch transaction in #28 (tracked in #34)
onto the Volumes layout.
- The managed AGENTS block says what to do once cognition is reliable: use
it as the repository-level system context by default, read only the
source, tests, configuration, and contracts the task directly needs, and
widen that evidence only when a specific missing fact could change the
answer; AOCI never replaces direct source evidence for the objects being
changed. One sentence in both locales, under "Establishing, generating,
and restoring cognition"; the rendered AGENTS.md and its golden follow.
Condensed from dignfei's AOCI-first reading wording in #28 (tracked in
#34); the runtime rules are unchanged.
- verify, check, and status on a Volumes repository tell a person
what is misaligned and what to do next. verify opens with the verdict
(Governance: aligned — 6 Entries cover 6 index-role sources, or the
result and its finding count), then lists Missing, Stale, Orphan,
Unbaselined, and review-pending Observe paths one per line, any other
actionable finding, and a Next: line naming the command or Agent action
that clears it; check prints the same lists under its verdict; status
adds one Governance: line with the result and the drift counts, computed
from the same governance facts through the fingerprint cache without
saving it, and status --json carries them under governance. Until now
the Volumes branch of verify printed "candidate structure is valid" and
three hashes before exiting 1, check printed a token and a count, and
status said nothing about alignment, so the paths behind a finding were
reachable only through --json. The init Scope Proposal line renders its
largest directories as text (./ (index 2, observe 0, exclude 0)) instead
of Go struct syntax, scan says "one Maintain round" when it means one,
and docs/getting-started.md says that init's own files count among the
index files scan reports and which formal assets to commit.
- A declared, enabled database source counts in governance before its
Database Volume exists. The absent-Volume branch of the shared governance
facts assessed no sources at all, so a repository could run database
source add, never snapshot it, and stay aligned: verify, check, Maintain,
and Guide all said so while database cognition status alone said
snapshotorrepairevidence. Now that source is an evidenceunavailable
finding, the verdict is evidence_required with
snapshotorrepair_evidence as the next action (Maintain stops with the
snapshot and accept commands), and accepted Evidence with the Volume still
absent routes to bootstrapdatabasecognition, which baseline accept
runs itself under automation.mode=auto. Bootstrap needs only Code
governance, so the verdict never blocks the command that clears it; a
disabled source and an engine without a collector stay informational.
Found on the SQLite walk-through, which also fixed what a person sees on
that path: the unsupportedcatalogfeature error names the operation and
the table (operation=catalogquerysqlite_check, object=t), database
source --help names SQLite, and the aligned verdict counts Database
Entries (6 Code Entries cover 6 index-role sources; 2 Database Entries
are bound to accepted Evidence).
- The Legacy-to-Volumes migration wa
AOCI-CODE v0.1.12026-11-04
AOCI-CODE v0.1.1 is built from a9b803fa47ac2a9c3a2da48209c9030db513612d.
A security update of the PostgreSQL driver. Nothing else changes: the Go
toolchain, the other dependencies, the MCP tool surface, input schemas,
formal-asset formats, and scope identities are those of v0.1.0, and a
repository aligned under v0.1.0 stays aligned. Upgrade if a PostgreSQL
source's connection string uses requireauth or channelbinding=require
without sslmode=verify-full; MySQL and openGauss sources do not use this
driver.
- Update the PostgreSQL driver github.com/jackc/pgx/v5 to 5.12.0, which
moves github.com/jackc/puddle/v2 to 2.2.3. pgx 5.12.0 fixes
GHSA-95fj-3fxw-g62g: from 5.9.0, a server could skip the authentication that
requireauth or channelbinding=require demanded, so a PostgreSQL source
relying on those without sslmode=verify-full could be answered by an
impersonating server. AOCI sends only fixed catalog queries, so the exposure
was a forged snapshot, not business data. GHSA-j38q-h3ph-jjpq does not reach
AOCI, which never sends simple-protocol batches. The release module set is
the same 22 modules, and both license texts are byte-identical.
- Known issue, unchanged from v0.1.0: running aoci cognition onboard apply
again on an onboarding that already completed writes the session back to
applypending, then answers onboardingartifact_conflict. The formal
assets and the Baseline are untouched, and Verify, Check, and the Guide
still report aligned; only the transaction and approval states that
cognition onboard status reads from .aoci/onboarding/active.json
disagree. Run Apply once. The v0.2.0 line returns the recorded result
instead and repairs a session left this way.
See docs/install.md and docs/supply-chain.md for asset verification.
AOCI-CODE v0.1.02026-11-03
AOCI-CODE v0.1.0 is built from d28f487be3990f9ce67ffeefa38df70e1fc5a22b.
The first release. It promotes v0.1.0-rc23 unchanged: the product code,
dependencies, Go toolchain, MCP tool surface, input schemas, formal-asset
formats, and scope identities are those of 592e90c, released as rc23 on
2026-10-29 and soaked since then. The soak found one defect, listed below as
a known issue. It is not fixed here, so the release stays the build that was
soaked. The 23 candidate sections below record how it got here.
- The release is no longer a candidate. The GitHub Release is published as the
latest release rather than a pre-release; the version pointers in the
READMEs, docs/install.md, docs/supply-chain.md, and NOTICE name v0.1.0;
and the release workflow's dispatch default moves with them.
- No behavior change. A repository aligned under rc23 stays aligned, and the
upgrade axis orders v0.1.0 after every candidate.
- Known issue: running aoci cognition onboard apply again on an onboarding
that already completed writes the session back to apply_pending, then
answers onboardingartifactconflict. The formal assets and the Baseline
are untouched, and Verify, Check, and the Guide still report aligned; only
the transaction and approval states that cognition onboard status reads
from .aoci/onboarding/active.json disagree. Run Apply once. The v0.2.0
line returns the recorded result instead and repairs a session left this
way.
See docs/install.md and docs/supply-chain.md for asset verification.
AOCI-CODE v0.1.0-rc23预发布2026-10-29
AOCI-CODE v0.1.0-rc23 is built from 592e90c80dac137950a8c871a2030300c516353b.
The rc22 soak's one finding: a Managed Scope rule could reach a formal
Volume and leave the repository with no command that moved it. Formal assets
are now outside policy. No MCP tool name, input schema, formal-asset format,
or scope identity changes.
- A scope rule that reached a formal Volume no longer deadlocks Managed Scope
(#158, Loren-0101). A rule could give aoci.code.txt the observe role, and
the Baseline then carried the Volume as Observe evidence that status, the
Guide, and a Scope Change Plan each read differently: the Guide reported it
observed_removed, scope acknowledge answered
observedevidencereviewnotpending, and every scope preview answered
observedevidencereview_required, with no command that moved the
repository. Formal assets are now outside policy: evaluation gives the Root
and its declared Volumes the index role whatever rules match them (a
git-hidden one still stops scan), the three readers strip them through one
projection, a Volume's Baseline record carries the index role however it was
recorded, and scope rule add or update refuses an exact file rule naming
one as managedscoperuletargetsformal_asset (switching such a rule
off is allowed). A repository already in that state is aligned again on
upgrade, and its next Scope Change writes the role back. No identity, tool,
schema, or format changes.
- The pre-tag audit of that fix caught two readers it had missed. The pin is
decided by the Root marker, so it never reaches a Legacy index file: there
aoci.txt is an ordinary rule-governed candidate whose Entry Maintain never
plans, and pinning it left an rc22-aligned Legacy repository with a custom
profile or a .txt rule answering managedscopeauthoringcandidate_required
for its own index with no command that cleared it. The post-Apply alignment
inspector that every aociupdateentry result reads now takes the same
projection as status and the Guide, so a Root or Meta record a rule once
observed no longer makes each batch report observed_removed while
governance says aligned.
See docs/install.md and docs/supply-chain.md for asset verification.
AOCI-CODE v0.1.0-rc22预发布2026-10-25
AOCI-CODE v0.1.0-rc22 is built from 0a0584f58aa823f8a18236dd8f181ccfbff3f184.
The rc21 soak's findings and nine contributed fixes: the S hard limit is the
Meta rune quota, a blocked Maintain names its blocker, scope acknowledge
retires an excluded Observe fingerprint, Maintain candidates carry source-bound
scale evidence, hooks fail open on configuration errors, a symlinked --repo
is its own Git root, and the base toolchain moves to Go 1.26.10. No MCP tool
name, input schema, or formal-asset format changes; two additive candidate
fields and one wider next_action vocabulary.
- Toolchain: Go 1.26.10. govulncheck reported GO-2026-6809 (crypto/x509
trust in compromised intermediate certificates, reached through the status
page's HTTP server) against 1.26.9 from 2026-10-21 on; the nightly Full
gate was red on the released tree until the base toolchain moved. No
source, contract, or asset change.
- The S hard limit is the Meta rune quota (#146). The per-C S token band is
floored by the effective rune quota, so an S within the quota the authoring
contract states is never entryfieldbudget_exceeded; a CJK Entry at C7
was being refused at 80 of its declared 200 characters. The S maximum
reported in Maintain and optimization candidates is the floored value. R
bands are unchanged. Public contract: Managed Scope and Budget v1, section 8.
- A blocked Volumes Maintain names its blocker in next_action (#147):
explicitorphanremoveorresolve_blocker only when
orphanremovecandidates lists something, otherwise
closependingrecovery, scantoestablish_baseline,
activatescopechange, acknowledgeobservedevidence,
resolvecognitionbudget, or resolveblocker. nextcommands is
unchanged. Public contract: Cognition Volumes v1, next_commands section.
- scope acknowledge retires an Observe fingerprint that an aligned policy
now excludes, instead of refusing the whole review set with
observedevidencereview_required once another Observe path changes
(#137, reported in #134).
- Volumes Maintain and cognition_optimization Code candidates carry
advisory filelines and expectede, counted and hashed from one byte
stream and emitted only when the digest equals the issued source_sha256
(#143, #142). Public contract: Cognition Volumes v1.
- Hooks fail open on configuration errors: a truncated config or unsupported
locale no longer makes aoci hook pretool or aoci hook codex-compact
exit 3 before running, and pretool no longer migrates a legacy config
(#144). Public contract: CLI Runtime v1, hook configuration failures.
- A --repo spelled through a symlinked component (/tmp on macOS) is the
same Git root as its resolved spelling (#145).
- The optional model client classifies a non-2xx answer before reading its
body, and a timeout while reading a body is a timeout, not a network
failure (#139, #138).
- aoci ui --also <relative> --stop and a second --detach find the page
registered under the absolute root (#140).
- The index parser strips every leading UTF-8 BOM, not one: a doubled BOM
left RawText starting with the second, so a Document re-parsed from its
own RawText changed (found by make fuzz-smoke; the input is a seed).
- Managed manifests no longer build an unused standalone Safe Inventory
(#133, refs #127); one Windows-only test assertion decodes the Guide JSON
before searching it (#141).
See docs/install.md and docs/supply-chain.md for asset verification.
AOCI-CODE v0.1.0-rc21预发布2026-10-14
AOCI-CODE v0.1.0-rc21 is built from cfa8e93ca9fe546a375f48b41b3d4766ed98b013.
Eight user reports, four contributed pull requests, and a test-system
upgrade: Volume removal keyed on the object's path, a Ledger that survives a
damaged line, activation that answers already_aligned, governed writes on
WSL DrvFs, MySQL 5.7.6 and later, localized refusals, private host-config
backups with a guarded status page, and a command tree that starts in
milliseconds instead of half a second.
- Backups written beside host configuration and formal assets are owner-only.
The optional model client refuses redirects and credential-bearing base
URLs, keeps a caller-owned HTTP client's own redirect policy, and reports
the status, the category, and a sanitized cause class (dns, refused, tls,
timeout, redirect) without the endpoint's error body or the transport
cause. No MCP or formal-asset schema changes.
- The loopback status page protects repository data with a per-process
capability carried in the readiness URL fragment and sent by the browser
in Authorization headers. The static shell contains no capability or
repository data, and a page opened without the fragment says which link
to open instead of rendering empty. Registrations keep their existing
shape; a tokenless page from an older binary can be stopped but is refused
by a new start, foreground or detached, until aoci ui --stop ends it.
- An out-of-band edit to a formal Volume under Managed Scope still fails
closed with managedscopeformalvolumebaseline_drift, and the refusal
now says how to recover: preserve the state, check pending Recovery through
the Guide, restore a verified matching snapshot when there is none, and
never edit Baseline hashes. The Legacy baseline scope refusal names the
same route, and docs/troubleshooting.md gains the section (#123).
- A Codex config declaring [mcpservers."aoci"] or [mcpservers.'aoci']
was reported as not installed and then given a duplicate bare table. The
installer and the status predicate recognize the quoted spellings, optional
whitespace, and a trailing comment, and leave such a config byte-for-byte
unchanged.
- Every aoci invocation built its command tree by decoding the embedded
localization manifest once per localized flag, several hundred times, about
half a second before the first byte of output. The decoded manifest is now
memoized once per process and the message reverse index is built once, so a
config get answers in a few milliseconds; human output is byte-identical,
pinned by the init, Guide, and help goldens.
- Fuzzing the parsers that consume external bytes found and fixed four
defects: an index warning could carry invalid UTF-8 into Findings and JSON;
a line whose name is only Unicode whitespace lexed as an Entry with an empty
name; an Attestation that repeated a challenge ordinal was scored every time
it appeared; and ./C:/x passed the drive-letter refusal of path
normalization. The carried openGauss connector panicked on a quoted
connection-string value ending in a backslash, from every parser entry
point; the canonical patch now refuses it and internal/dbevidence also
recovers at its boundary.
- Tests: internal/cli tests run through the per-invocation executor instead
of package globals, so the package is order-independent (-shuffle) and
runs in seconds; internal/testkit holds the shared fixture, git, locale
and stdout helpers. Fault-injection tests cover the CAS rollback and
recovery states, the directory lock fallback, immutable archives, zero-write
closures, receipt storage, the Migration and Bootstrap codecs, replay
mismatches and safety approvals; make coverage-floors enforces per-package
statement-coverage floors for the safety core in full-confidence. Eleven
native fuzz targets with seed corpora run under make fuzz-smoke nightly.
- Black box: conformance repeats its locale-dependent checks under zh-CN (53
checks); scenarios gain group H for the pre-write hook and --group/--list
(75 scenarios); lifecycle bring-up covers git submodules, the
excluderootdirs roles, remove-entry, the machine documents, and a
zh-CN twin lane. The upgrade axis gains a downgrade shape, in which every
earlier release reads a repository the binary under test wrote (80 checks
per release over ten shapes), --self runs the candidate as both the
released and the under-test binary before a tag exists (make axis-self,
also in make verify and the release rehearsal), and --recent N layers
CI: a push runs the newest three releases, the nightly run every release.
The real-repository harness is tracked as scripts/blackbox/realrepo.py.
- scripts/blackbox/ladder.json registers every test contract that must be
run by name, with cadence, preconditions, and the last verification on
record; make verify ends by listing what is overdue and make ladder
prints it on demand.
- Nightly gates: the long-running cognition refresh harness runs again
(make longrun-refresh; it had drifted from the Attestation schema and the
repair finding shape since August), the seven first-party benchmarks are
compared against an advisory baseline (scripts/bench-compare.py, a
warning annotation above 30 percent, results uploaded as an artifact), the
carried connector's own test suite runs against the openGauss container as
an advisory step (300 pass, one server-behaviour difference on year-zero
dates), and the page JavaScript tests get an explicit Node 22.
- Removing a Code Entry keys on the object's path, so an orphan whose Entry
line is byte-identical to a line in another directory section (a staged
copy of the same file) goes while its live twin stays; the line-keyed
remover refused both as duplicates, and three such orphans held a
1,400-target authoring debt behind write_conflict (#117). A plain
repository-relative path under Volumes v1 names code:<path> and reaches
the Volume pipeline instead of the Legacy loader's volumereadonly
(#112); while a Managed Scope edit is pending, the orphan refusal says
scopechangerequired and names aoci scope activate --json, since
orphan proof follows the active Baseline. The remove-entry help states that
Volumes removal is orphan-only on both surfaces.
- A Volumes removal that had written the Volume and the Baseline but could
not complete its Ledger event left a receipt nothing could close and
removeledgercompletion_failed carried no reason (#121). A Ledger line
that does not decode is now skipped by the terminal-event check, a line
over 1 MiB counts as one corrupt line instead of ending the read, the
failure names its cause, and a disabled Ledger is refused before anything
is written.
- aoci scope activate reports already_aligned with exit status 0 and
records no transaction when the desired policy, budget, and authorization
posture already equal the active receipt and nothing would move; it used
to file a zero-change transaction and report it as "applied" (#113).
scope status and scope show carry repository_root.
- When a Volumes v1 policy edit blocks aocimaintain, nextcommands and
the Volumes Guide name scope activate --json beside scope status --json
instead of looping between status and Maintain (#118; contributed by
dayebishouji in PR #119).
- Twenty-six CLI commands rendered their English short description under
every locale because the hand-kept localization map had no entry for them
(scope budget and its subcommands, observe-policy, approval-mode,
authorize, source, capabilities, cognition onboard, baseline
scope); all are mapped, and a test walks the visible tree under zh-CN.
The PreToolUse hook injected hardcoded Chinese text into every host; its
six texts now come from the UI catalog in both locales, byte-identical
under zh-CN.
- repair_required findings about
AOCI-CODE v0.1.0-rc20预发布2026-10-09
AOCI-CODE v0.1.0-rc20 is built from 45990a1dcfc4415efdc6fbfa13bc159a415f127c.
Five user reports and two contributed pull requests: an E scale audit,
submodule boundaries, refusals that name the working path, root-anchored
artifact names for new repositories, and a benchmark.
- verify and check audit each Code Entry's E scale letter against the
source line count under the Meta's bands and report the mismatches, as
information that never changes the exit code (e_scale in --json);
aocimaintain with intent=cognitionoptimization ranks such Entries for
review after high-importance Entries without an S, with selection reason
escalemismatch (#103, reported by @Rosenls). Through rc19 the letter was
checked only in the Legacy layout.
- A git submodule is reported as a git_submodule boundary instead of an
unsafefilesystemobject: scan says how many submodules it left alone,
and scope explain on a path beneath one names the boundary (#107, reported
by @zsjlfb). Indexing a submodule's code still means initializing the
submodule itself.
- The refusals a stale Managed Scope Baseline meets now name the path that
works: scan --force points at aocimaintain, aociremove_entry, and
aoci scope activate, and baseline scope plan/preview say they are the
Legacy refresh (#102, reported by @Lixiang9716).
- Docs: the index format contract states that an Entry's leading name is the
bare file name within its directory section (#103); the README's execution
mode table marks endpoint-native drafting as Legacy-only and says what the
ai configuration block serves in a Volumes v1 repository.
- New repositories get excluderootdirs (#104, PR #105 by @dayebishouji):
init persists backup, backups, build, cache, coverage, dist,
target, tmp, uploads, artifacts, and vendor there instead of in
exclude_dirs, so those names exclude a directory at the repository root
or wherever git ignores it, while a tracked nested src/build/tool.go or
views/monitor/cache/index.vue is source. A git-ignored nested directory of
such a name stays one inventory line (#97). Existing repositories keep
their any-depth exclude_dirs and their identity; opting in is a config
change plus aoci scope activate. config get/set, doctor, and
scope explain know the field; the upgrade axis gains a legacydirs shape
and publishes 72 checks per released version over nine shapes. A repository
that carries the field needs rc20 or later on every machine: an older
binary demands a Scope Change over it and drops the field when it saves the
team configuration. The Baseline reads Entry paths through the same lists
as the inventory, so an Entry under a root-excluded directory is skipped
rather than reported as an orphan; config set on either directory list
takes build/ as build, drops duplicates, and refuses app/build, which
could never match.
- Toolchain: Go 1.26.9. govulncheck reports nine standard-library advisories
against 1.26.6 (GO-2026-6603, 6605, 6607, 6608, 6610, 6611, 6612, 6613,
6617 in net/http, net/textproto, and crypto/tls, which the status
page and the database drivers link), all fixed in 1.26.9; release binaries
are built with it and go.mod requires it.
- Tests: the 1,000-object governance timing moved from a five-second
wall-clock assertion to a benchmark that full-confidence runs (PR #108 by
@dayebishouji).
See docs/install.md and docs/supply-chain.md for asset verification.
AOCI-CODE v0.1.0-rc19预发布2026-10-08
AOCI-CODE v0.1.0-rc19 is built from 0864b1aaed840c4ef15fb4f8bb365099ef578ce4.
Two fixes from user reports: Scope Change replay, and directory names that
hid source from the index.
- Scope Change replay no longer depends on files other tools write (#101).
A Git-ignored path that no rule governs and that the active Baseline does
not hold leaves the transaction envelope, and the candidate count and
selection identity the envelope carries are recomputed from the paths kept,
so a lock or cache file appearing between scope preview and scope apply
(CodeGraph's watcher, for one) no longer ends in deterministicreplayfailed
or managedscopereplay_mismatch. A preview minted by rc18 or older fails
replay once after the upgrade; run scope preview again. .codegraph is a
built-in runtime directory like .aoci. Found and diagnosed by @Zedthm and
@mahirhir.
- Directory names that can denote source are no longer a built-in safety rule
(#100). Through rc18 backup, backups, build, cache, coverage,
dist, target, temp, tmp, uploads, artifacts, and vendor were
matched against every path component and hard excluded with no way back:
src/backup, views/monitor/cache, and tests/api/coverage were dropped
from the index silently. The built-in rule now keeps only names that never
denote source (nodemodules, pycache__, .next, .nuxt, .output,
.cache, the third-party distribution names); the rest are governed by
exclude_dirs, which init already writes into .aoci/config.json, so an
existing repository changes no role on upgrade and now has a door: remove
the name with aoci config set exclude_dirs ... and run
aoci scope activate. scope explain reports a configured exclusion as
excludedirs:<name> or excludefiles:<pattern> instead of
project_config. Two names were never in the default list: a tracked module
under a nested cache/ or temp/ becomes a Missing Entry after the upgrade
and is authored like any new source; a git-ignored one stays excluded but is
listed per file rather than collapsed unless exclude_dirs names it.
- Black-box: a scenario plants a file in a git-ignored directory between
preview and apply; the upgrade-axis fixture carries a tracked module named
backup that every release must keep out across the upgrade.
- Dependencies: golang.org/x/text 0.41.0 (GO-2026-6629, a panic on crafted
input in x/text/secure/precis, reachable through the database drivers'
SASL preparation) and golang.org/x/sync 0.22.0 with it.
See docs/install.md and docs/supply-chain.md for asset verification.
AOCI-CODE v0.1.0-rc18预发布2026-10-05
AOCI-CODE v0.1.0-rc18 is built from ffbdafac512d339aa87342d5b9d1a4f27a299aaf.
Inventory speed on large ignored trees, and a few host and CLI fixes.
- Safe Inventory no longer has git list ignored directories whose every file
was a hard exclusion anyway (#97). The ignored listing now uses
git status --ignored=matching: a git-ignored node_modules, dist,
target, or other built-in generated, runtime, or VCS directory, and any
directory named in exclude_dirs, is one inventory line instead of one entry
per file on every scan, verify, and Maintain, and a pnpm workspace whose
package links form a cycle no longer runs forever on Windows. Every other
ignored path is listed one by one as before (an ignored gen/ or out/, and
ignored files inside untracked directories), so no candidate, rule outcome,
opt-in, role, or persisted identity changes on upgrade; a test pins the
candidate set and identities against the full listing. git before 2.16 falls
back to the full listing.
- When the inventory's git query fails, init, scan, scope, and
source manifest keep the machine code (safeinventorygitqueryfailed)
and print git's own stderr, verbatim and bounded to its last 2 KiB, on the
next line of stderr, in human and --json modes alike; the localization
notes record this as the one verbatim exception. verify, check, and
Maintain report the failure as a business-source finding, so run
aoci scan to see git's message. scope explain reports a path under an
exclude_dirs directory as a configured exclusion.
- config list, config get, and config set honour the global --json
flag (#94, PR #95 by @dakjdakd): typed JSON values for get, and an
{ok, key, value} result for set whose value is what the next
config get returns (local overrides included); setting locale adds
restartmcprequired and, when a migration is pending, a
locale_migration summary with the numbers human mode prints. Output goes
through the command writer; human-mode output is byte-for-byte unchanged.
- init --agent qoder writes the project-level .mcp.json that Qoder CLI
reads (verified with qoder mcp list), the managed AGENTS.md block, and
no hook; doctor and the aoci ui status page gain a Qoder row (backed by
that shared file), and Detect recognises a project .qoder directory or a
user-level ~/.qoder. The Qoder IDE takes the same mcpServers block
through its settings.
- The Maintain authoring instructions now say that batches are not user
decisions: after a successful write the model calls Maintain again until
remaining is 0 without asking the user to continue. A Qoder session had
stopped after the first of 53 batches to ask.
- github.com/spf13/pflag 1.0.9 to 1.0.10 (PR #93); module set unchanged.
- Black-box: lifecycle bringup plants an ignored node_modules tree with a
symlink cycle and asserts the inventory collapses it; the upgrade axis gains
shapes for a rule-pulled file inside an ignored directory and for an ignored
node_modules tree; a Windows test builds a junction cycle inside an ignored
node_modules.
- Fix the repair guidance for a mistyped or self-computed Code binding. Since
rc16 the Maintain response no longer repeats code_plan.candidates, but the
codecandidatesourcesha256mismatch, codecandidateid_mismatch, and
codecandidatepath_mismatch repair actions still told the model to copy
the value from there, so a first build whose model had hashed a file itself
was refused with zero writes (correct) and then could not recover. The
actions now name the Maintain response's candidates list and the finding's
own expected value, the source_sha256 action says never to compute the
hash, and the cause states the fact the server has already checked: the file
on disk still matches the issued binding, so the submitted value came from
other bytes. Black-box B4 requires the finding to be recoverable from the
response alone.
See docs/install.md and docs/supply-chain.md for asset verification.
AOCI-CODE v0.1.0-rc17预发布2026-09-29
AOCI-CODE v0.1.0-rc17 is built from 93d6ad5a87fd9624a51cae61b2134d33944501fb.
S coverage on high-importance Entries. A real-repository build under Codex
came back with S:- on 78 percent of its Entries and on two thirds of its
C7-C9 ones, and a source audit found most of those were misses. The authoring
contract, the Guide field rules, and the public S discipline now say where to
look before writing S:- on a C6+ object: the implementation behind an
interface, the aspect or interceptor that wraps it, the SQL, templates, or
scripts it executes or feeds, the configuration that overrides it, and the
cache, transaction, soft-delete, and uniqueness rules on its persistence path;
a C7+ S:- written without that look is as wrong as an invented S. The
starter Meta example is now a C7 Entry with every field filled and an S one
sentence long inside the C7 band, where the previous starter showed
R:- | A:- | S:-. Existing repositories keep their Meta bytes.
- aoci verify, aoci check, aoci scope status, and the Maintain
governance.budget carry s_coverage: Entries and Entries with S per C
band, plus the count and share of C7+ Entries without S. check prints one
line and, at or above the machine hint threshold of 25 percent, suggests one
cognition_optimization pass. A hint, never a gate.
- cognition_optimization reviews C7+ Entries without S right after budget
overage and before plain C order. Each candidate carries selection_reason
(new value sabsenthigh_importance), and the batch instructions say that
returning such an Entry unchanged is a valid result.
- aoci init with the production profile persists seven starter observe
rules (starter-vendored-*, source builtin) for vendored static assets
and generated bundles: libs, lib, and plugins under static/,
.min.js, .min.css, *.map, and fonts/. A first build no longer
authors Entries for jQuery or Bootstrap. Written only when no config
exists; DefaultPolicy, the built-in profile rules, and existing
repositories are untouched, a user rule overrides a starter rule at any
order, and aoci scope rule remove drops one before the first scan
without approval. (vendor, dist, and build directories were already
refused by the safety boundary.)
- make update-goldens also regenerates the prompt snapshot digests.
- Black-box: 64 fault-injection scenarios (O2 checks the optimization review
order, reason, and unchanged-batch completion); the lifecycle suite asserts
the starter rules after init and scan.
See docs/install.md and docs/supply-chain.md for asset verification.