Nautilus

Nautilus / Quanta — Tier-C Interface Specifications

This directory holds the published interface specs that let third parties integrate with Nautilus and the NT Connect sibling products without running the closed NT Connect services. See docs/requirements-and-features.md §14 for the three-tier model (open primitives, closed services, documented interfaces).

Specs in this directory

Spec Status Scope
ship-pbx.md Draft v0.1 Legacy on-vessel PBX (Avaya / Mitel / Cisco / Alcatel / Asterisk / FreeSWITCH / etc.) integrates with the Nautilus bus for call events, PA/GA, E911, recordings, and commands. Retrofit-first.

Specs planned (see OQ-24)

Priority order:

  1. Heimdall content-safety API — the REST contract for /analyze, /moderate, /moderate/conversation, /moderate/image, /moderate/video; audience tier enum; verdict schema; NCMEC-hook pattern.
  2. CallCraft agent contract — extends the Quanta agent contract (AGENT_MESSAGES / AGENT_RESPONSES) with voice/video-session semantics so third-party AI agents can participate in calls/rooms.
  3. ConnectOne E911 / PA-GA / muster signaling — the concrete subject contract and priority semantics for Nautilus muster and safety flows when ConnectOne (not a legacy PBX) is the telephony platform.
  4. Quanta keys-service protocol — key-bundle format and verification so third parties can implement a Quanta-compatible keys-service.
  5. iTV / cabin GRMS adapter contract (OQ-16) — lighting, HVAC, drapes, safe, minibar, door-lock abstraction behind a pluggable adapter.
  6. Fleet-wide federation — ship-to-ship and ship-to-shore subject routing for multi-vessel tenants.

Licensing

  • Spec text — Creative Commons Attribution 4.0 (CC BY 4.0).
  • Reference stubs + conformance test harnesses — Apache License 2.0.

Implementers do not need to use any NT Connect code to build a compliant integration; implementing against these specs alone is sufficient. NT Connect's managed services (Quanta, ConnectOne, CallCraft, Heimdall) are the reference commercial implementations of the same specs.

Convention

Each spec contains:

  1. Purpose & audience.
  2. Integration model (the 30-second picture).
  3. Authentication & authorization (transport, JWT claim schema, capability model).
  4. Subject / endpoint contracts.
  5. Payload schemas.
  6. SLAs and delivery semantics.
  7. Priority / emergency handling (where applicable).
  8. Tenant isolation.
  9. Retention & data handling.
  10. Conformance testing.
  11. Security considerations.
  12. Known unknowns / TBD.
  13. Relationship to Nautilus requirements (FR / NFR / F-Dxx / OQ references).
  14. Licensing.