Frequently asked questions

Do I have to build the frontend in Acore?

No. Existing Flutter, React, and web applications can consume generated client surfaces, and any application can keep its current networking stack while using AxiomCore for contract review, mocks, tests, and release evidence. Acore UI is an optional alpha application-authoring path.

Do I have to write my backend in Acore?

No. FastAPI is the primary extraction path, Go extraction is alpha, and bounded OpenAPI/SQL bootstrap paths are experimental. You can also author the contract directly. Acore describes and composes the contract; it does not require rewriting all backend implementation code.

Does backend extraction execute my service?

It can. The current FastAPI extractor imports and executes the selected module's top-level initialization to obtain the application object. Keep imports safe, install required dependencies, and move production connections or worker startup behind explicit process entry points.

Are .axiom and .axiomapp the same artifact?

No. .axiom carries a compiled contract. .axiomapp is a target application artifact containing the verified Acore UI payload and target host material. Both are non-source artifacts with their own manifests and verification rules.

Does a signature make the contract secure?

A signature proves provenance of exact bytes relative to a public key. It does not prove backend authorization, source correctness, privacy, compatibility, or test coverage. Use locks, semantic diff, security analysis, tests, and release policy as separate controls.

Are browser and native requests guaranteed to behave identically?

They share contract concepts but use different network, cache, lifecycle, and framework bridges. Browser CORS/cookies and sessionStorage differ from native HTTP and an optional Sled path. Run end-to-end tests on every shipping target.

Is ATMX “zero JavaScript”?

No. ATMX includes a JavaScript integration layer and Wasm runtime. Its DOM scanner can reduce application glue, but startup, framework code, browser policy, and some declarative expression evaluation remain JavaScript boundaries.

Where should authentication secrets live?

In the application's appropriate secure/session storage or a scoped runtime configuration channel. A contract can declare where authentication is attached, but production credentials should not be committed in Acore, generated clients, locks, mocks, screenshots, or source control.

Can I use AxiomCore in CI?

Yes for headless commands such as validation, test, build, lock verification, semantic diff, and selected UI checks. Install the chosen extractor and its required service dependencies. Pin tool and contract versions, avoid interactive selection, and fail on non-zero exit status.

What happens when the backend violates a response contract?

Where response validation is implemented for the selected runtime and endpoint, the operation reports a structured validation or decoding error. It does not guarantee that every UI will recover gracefully; the application must render the error state and decide whether retry or fallback is safe.

Is the Axiom Marketplace available?

Not yet. Typed package formats and lock tooling are alpha, but a supported catalog browsing and installation workflow is coming soon. Axiom Studio and Acode are also coming soon; existing dashboard, language-server, and editor foundations should not be mistaken for those finished products.

Can Cloud replace GitHub and all CI/CD today?

No. Axiom Cloud manages Axiom contracts, their release evidence, channels, environments, tests, reviews, and runtime observability. General repository hosting and arbitrary CI/CD replacement are outside the current documented boundary.