Add OMOS starter architecture and OT conversion API

[ohi-stack]

Motivation

• Provide a deployment-ready OMOS starter system that mirrors the four-layer architecture (Identity → Algorithm → Protocol → Institution) and exposes it as an API surface.
• Implement a deterministic OTS‑V5 time layer (OT ↔ UTC) and runtime alignment enforcement so protocol documents become executable code.
• Scaffold canonical repository seeds (omos-core, onegodian-time, onegodian-agent) so the repo structure maps to the institutional architecture.

Description

• Added an OMOS API under /api/omos with endpoints POST /classify, POST /align, POST /timestamp/convert, and POST /decision/run wired into the main router (src/routes/api/omosRoutes.js, src/routes/index.js).
• Implemented core OMOS services: identity classification (src/services/omos/identityService.js), alignment checks with a system prompt loader (alignment/system-prompt.txt and src/services/omos/alignmentService.js), algorithmic decision pipeline (src/services/omos/algorithmService.js), and OTS‑V5 time conversions plus record builder (src/services/omos/timeService.js).
• Added controller handlers (src/controllers/omosController.js) that expose service behavior as JSON APIs and updated documentation (README.md, docs/omos/repo-architecture.md) to list the new endpoints and architecture mapping.
• Created in-tree starter repo scaffolds and supporting artifacts (omos-core/, onegodian-time/, onegodian-agent/) including an openapi.yaml, kernel decision stub, OT engine bridge, and agent template, plus integration tests (test/omos.test.js).

Testing

• Ran the integration test suite with npm test which passed all tests (6 tests, 0 failures).
• Ran static checks with npm run check which completed without errors.
• Executed enforcement validation with npm run validate:enforcement which returned Enforcement validation checks passed.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2ae45908d1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Reject timezone-less UTC timestamps in OT conversion

buildTimestampRecord accepts any date string and parses it with new Date(inputUtcIso), which treats values like 2025-03-18T00:00:00 as local time instead of UTC. That makes the same API request produce different OT results across server timezones (and can incorrectly throw “predates OT epoch” in positive-offset regions), so the conversion is not deterministic as designed. Require an explicit Z/offset or parse/normalize strictly as UTC before calling utcToOt.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Bound OT dayOfYear during input validation

validateOtInput only enforces dayOfYear >= 1 and never checks the upper limit for the specified year, so impossible values (for example dayOfYear: 999) are treated as valid. Any caller using this validator as a gate can accept invalid OT timestamps and fail later when conversion logic rejects them, so this validator should enforce the same 365/366-day constraints as otToUtc.

Useful? React with 👍 / 👎.