Skip to main content

Source contracts

  • /health: application identity, process uptime and the configured runtime source revision.
  • /api/v1/marketplace/listings: HTTP 501 while the marketplace adapter is unavailable.
  • /api/v1/town/ticker: HTTP 501 while the activity adapter is unavailable.
  • /api/v1/town/feed: HTTP 501 while the activity-stream adapter is unavailable.
  • /api/v1/runtime/status: a status payload containing hardcoded deployment and performance counters.
  • /api/v1/newsletter/subscribe: validates a submitted address and forwards it to the canonical MailGenie public-lead route; this is a write action.
No production newsletter message or contact was submitted as part of the documentation setup. A source route is an implementation contract, not a delivery receipt. Runtime status counters, sample gate totals and displayed latency values require measured evidence before being presented as live results.

Google and Eyedbase

The selected owner is devtown.ai@gmail.com. The project is devtown-production; the upstream Google callback is the production Eyedbase google-devtown broker endpoint. The issued pair is retained in infrastructure’s protected/masked identity/prod authority. The configured broker and product OIDC consumer are separate from real sign-in and tenant authorization acceptance. The current deployed native consumer reports OIDC_PRODUCT_SESSION_UNAVAILABLE until its allocated persistence/TLS/credential contract is ready. Do not place secrets in public documentation or browser code.

Product boundaries

Eyedbase owns identity. Fleetboots owns fleet execution, Mechscrum owns workplans and workflow orchestration, and EyeParity owns visual testing and proof custody. DevTown presents approved product interfaces without establishing those integrations from static UI content or counters.

Mintlify delivery

The assigned owner is the same DevTown app owner. The actual organization/project is dev-town/dev-town; source lives in the private DevTown repository, branch master, content root mintlify. The account was created on October 25, 2026 under the assigned owner. Vendor-issued TXT records were retained, published and publicly matched before the CNAME was created for docs.devtown.ai. The three guides are published, the custom domain reports Connected, and all three routes returned HTTP 200 over normal TLS. Automatic private GitLab source synchronization remains unaccepted. Documentation delivery does not establish a native DevTown login.