Skip to content

Add explicit Console machine access to Alia chat - #1577

Merged
NateIsern merged 13 commits into
mainfrom
fix/1571-alia-machine-principal-20261004
Oct 4, 2026
Merged

NateIsern merged 13 commits into
mainfrom
fix/1571-alia-machine-principal-20261004

Conversation

@NateIsern

@NateIsern NateIsern commented Oct 4, 2026 •

Copy link
Copy Markdown
Member

Console-issued machine credentials can explicitly opt into Alia chat with both alia:chat and inference:invoke. The SDK supplies a separate typed application principal and uncached Alia-scoped introspection. The API checks canonical credential authority; migration 0143 expands three scope vocabularies without granting existing credentials new permissions. Console exposes the explicit scope pair, and the generated OpenAPI schema includes it.

This change prepares @oxy.so/core@4.4.0. The backend must be deployed and accepted before publication; Alia#666 then adopts the verified registry release. The Alia companion limits machine requests to stateless application chat and charges the calling application's inference relationship.

Validation: source-bound core 14, API 60, real membership SQL 7, Console 6 UI + 2 edge checks; strict builds/types and scoped lint pass. Root additionally verified the 4.4 candidate build, package formats and 2,249 core tests in 185 suites, and composed the production chat-budget correction #1579. The OpenAPI freshness guard passes after regenerating the three changed scope enums. Original source/test proof retains its historical source pins; release metadata, ADR acceptance and generated OpenAPI follow-ups are recorded in the later commits.

No production caller is granted access by this change. Actual publication, adoption and runtime acceptance remain pending. Tracks #1571; the broader service-access model in #873/#874 retains its own criteria.

@NateIsern

Copy link
Copy Markdown
Member Author

Root review of source c8f60f2 (Oxy) /69e0d85a (Alia), plus release preparation255df40a:

Verified36 source files against their Git commits and24 evidence records. Reviewed the SDK receiver/audience/environment boundary, canonical live machine resolver, caller-owned inference payer, request-scoped bearer storage, no owner-to-user conversion, restricted chat entry and empty tool pipeline. Console capability opt-in preserves untouched scope lists; SQL migration0143 widens three CHECK vocabularies without granting rows. API60, core14, Console UI6+HTTP/SQL7 and Alia112 focused tests, including old auth RED, are recorded.

Core4.4.0 preparation changes only package version, lock version and changelog. Full core types/build/package-format checks pass;2249 tests/185 suites pass. Candidate tarball585 members, SHA2561d6cb34ed0b1bf14e4776820a25f9ff29de80ead6b6636fc1525538baa8071a4. No package published yet. Backend migration and endpoint must be accepted before root rebuilds/packs/publishes from protected main; Alia666 must then adopt the actual registry package and rerun its consumer checks. This does not close generic service-grant epics or prove a funded third-party production invocation.

Holding this promotion behind incident1579 so the chat-budget repair reaches production first.

@NateIsern

Copy link
Copy Markdown
Member Author

La reparación urgente de Alia #1579/#1581 ya está desplegada y aceptada con respuesta real del payload completo Hello/21 herramientas/Auto: HTTP200, texto, stop, sin tool calls y recibo v2 completado d605d4a3-cef7-4f00-95e3-4c0358525133. Fuente main3c0d, API699/worker211, imagen7f63c68c. La observación separada de costes no se equipara a factura.

La revisión de #1577 sigue vigente en head0fc1512f1b836751946c73ab42c96ebe367e6402. La composición aislada con main3c0d no tiene conflictos y preserva las hojas SDK y lock revisadas, así como la política High. Se habilita la cola normal; el backend y la migración0143 se verificarán antes de publicar core4.4 y adoptar Alia#666. No hay bypass de CI ni activación de claves/grants predeterminados.

@NateIsern
NateIsern added this pull request to the merge queue Oct 4, 2026
@NateIsern
NateIsern removed this pull request from the merge queue due to a manual request Oct 4, 2026
@NateIsern

Copy link
Copy Markdown
Member Author

El primer intento de cola8b2 falló únicamente al comparar las mismas filas de claim en distinto orden SQL (shard4:1490PASS/1FAIL; HTTP503 y executions0 correctos). Fuente runtime/SDK/política sin cambios. Se añadió ORDER BY id sólo al helper de snapshots y se validaron65controles HTTP/SQL/económicos en PostgreSQL propio; fallo original preservado.

Main3c0d compuesto sin conflictos,70hojas preservadas; candidate core4.4 conserva585miembros/SHA1d6cb34. Root verificó7refs de la corrección y los árboles completos cab3597/723839290 son idénticos. Proof integrado mantiene ambos pins y enlaza fuente accesible en la rama del PR. No publicación ni nuevo despliegue por este seguimiento. Se vuelve a habilitar la cola normal con la cabeza exacta actual.

@NateIsern
NateIsern enabled auto-merge October 4, 2026 19:25
@NateIsern
NateIsern added this pull request to the merge queue Oct 4, 2026
Merged via the queue into main with commit 0c6dec1 Oct 4, 2026
24 checks passed
@NateIsern
NateIsern deleted the fix/1571-alia-machine-principal-20261004 branch October 4, 2026 19:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant