Where Arc for TypeScript (and the Chronicle.TypeScript work it depends on) stands, what is in flight, and how to continue. Each item links to the issue that holds its details.
Recently released
Arc.TypeScript (GitHub prereleases; npm publication is still disabled):
Earlier: v0.40.0 through v0.43.0 (runInScope, PostgreSQL LISTEN/NOTIFY observation, co-located vertical slices, projection-backed given events).
Also merged without a release: AI corpus update (#117), CI fix for pull requests with an empty diff (#138, #109), documentation correction (#139, #133). Closed #35.
Chronicle.TypeScript (npm on merge), for #129 (EventScenario and ReactorScenario):
In flight
Next
Arc parity and integrations:
Chronicle.TypeScript parity with the .NET client (umbrella Cratis/Chronicle.TypeScript#58):
How the work is done
- One issue per change, assigned to its owner; one branch and worktree per change.
- Arc for .NET is the reference; its
Documentation/http-contract.md is the wire contract. Parity is claimed per area only with a passing executable check.
- In-process test harnesses (Chronicle
ReadModelScenario, EventScenario, ReactorScenario) support only behavior proven by a committed fixture from the pinned kernel oracle (yarn oracle:check); anything else is rejected with an explicit error pointing to a kernel-backed test.
- Every change is reviewed independently until it has no confirmed findings (cross-provider when available, otherwise a same-provider review that is stated as such), then local gates, then a PR with release notes in the repository template's sections.
- Local gates: run every step of the root
package.json ci script. The Library e2e needs a working cratis/chronicle:latest-development image (recently unreliable locally); hosted CI always runs it.
- Merge with a merge commit only (
gh pr merge --merge) once hosted CI is green; never squash, rebase or force-push. Minor and patch releases: gh release create vX.Y.Z --prerelease --target <merge commit>. No major release without an explicit human decision.
- Applications built on Arc for TypeScript keep a behavior's backend code, backend specs, generated proxy, React component and frontend specs in one slice folder (see
Documentation/vertical-slices.md).
Open decisions for the maintainer
Where Arc for TypeScript (and the Chronicle.TypeScript work it depends on) stands, what is in flight, and how to continue. Each item links to the issue that holds its details.
Recently released
Arc.TypeScript (GitHub prereleases; npm publication is still disabled):
Earlier: v0.40.0 through v0.43.0 (
runInScope, PostgreSQL LISTEN/NOTIFY observation, co-located vertical slices, projection-backed given events).Also merged without a release: AI corpus update (#117), CI fix for pull requests with an empty diff (#138, #109), documentation correction (#139, #133). Closed #35.
Chronicle.TypeScript (npm on merge), for #129 (
EventScenarioandReactorScenario):@childrenFrom(Let integrations take part in shutdown before Arc disposes services #127)In flight
Next
Arc parity and integrations:
activateArtifactsInScopesshould be on by defaultChronicle.TypeScript parity with the .NET client (umbrella Cratis/Chronicle.TypeScript#58):
How the work is done
Documentation/http-contract.mdis the wire contract. Parity is claimed per area only with a passing executable check.ReadModelScenario,EventScenario,ReactorScenario) support only behavior proven by a committed fixture from the pinned kernel oracle (yarn oracle:check); anything else is rejected with an explicit error pointing to a kernel-backed test.package.jsonciscript. The Library e2e needs a workingcratis/chronicle:latest-developmentimage (recently unreliable locally); hosted CI always runs it.gh pr merge --merge) once hosted CI is green; never squash, rebase or force-push. Minor and patch releases:gh release create vX.Y.Z --prerelease --target <merge commit>. No major release without an explicit human decision.Documentation/vertical-slices.md).Open decisions for the maintainer
activateArtifactsInScopeson by default.