Skip to content

Core overview

Core is the shared Java and Spring Boot application programming interface (API) service for 9L-SRE. Both ClientJ and ClientL use the same service for issue tracking. Its repository is 9l-sre-core.

Core owns issue-tracking data and shared business rules: workspaces, issues, comments, statuses, planning intervals, users, attachments, and workspace-specific role assignments. A User represents the operative’s account and profile in the issue tracker; character backstory is outside this model.

Both clients should interpret identifiers, status values, validation failures, and data lifecycle consistently. Their interfaces can differ without changing the meaning of a Core response. Integration plans are documented for ClientJ and ClientL.

The API pages describe proposed contracts, not verified implemented endpoints. ★ Minimum identifies endpoints for the first milestone.

  • Mock: proposed fixed issue reads under /mock, with fixtures and test requirements.
  • Auth: external sign-in and sessions under /auth.
  • Issues: issue creation, retrieval, listing, and updates under /issues.
  • Workflow: role-controlled status transitions under /workflow; deferred from the first milestone.
  • Comments: issue discussion under /comments; deferred from the first milestone.
  1. Authenticate externally and establish a verified User and UserIdentity.
  2. Assign the new reporter a role in the seeded workspace.
  3. Create an issue in Reported status.
  4. Retrieve it by ID for display.

Open decision: how the new reporter receives a workspace role. Automatic assignment to a seeded Reporter role has been proposed but not agreed. UserRole cannot be seeded ahead of a newly created User; this decision must be resolved before the end-to-end flow can be implemented.

Supporting resources are seeded; their management APIs are deferred. The initial demo uses an in-memory H2 database, so restarting clears created issues and users and restores the seeds. The Tables overview marks the minimum tables.

For each implemented operation, document its HTTP method and path, required identity or permissions, request fields, response fields, status codes, and validation errors. Include a request example checked against Core. Document filtering, ordering, and pagination when collection operations introduce those behaviors.