JS Globtech
44 documents
Architecture Decision Records (ADRs)⏱️2 min read

Architecture Decision Records

Short, dated records of significant technical choices for JSGlobtech. The goal is that six months from now you can recover the *reasoning*, not just the diff.

Architecture Decision Records

Short, dated records of significant technical choices for JSGlobtech. The goal is that six months from now you can recover the reasoning, not just the diff.

When to write one

  • Choosing or replacing a dependency, vendor, or hosting target.
  • Changing how leads are validated, stored, or delivered.
  • Anything where a future reader would reasonably ask "why was it done this way?".

Skip ADRs for routine content edits and refactors.

How to add one

  1. Copy 0000-template.md to NNNN-short-title.md using the next free number (0001-, 0002-, …).
  2. Fill in Status, Context, Decision, Consequences.
  3. Add a row to the index below.
  4. If the decision changes the stack or a vendor, also update ../architecture/README.md or ../integrations/README.md.

Superseding a decision: leave the old ADR in place, set its status to Superseded, and link the replacement.

Index

ADR Title Status Date
0001 GEO plus an MCP agentic layer as the core differentiator Accepted 2026-07-30
0002 /.well-known/llms.txt as the canonical AI-discovery artifact, with a /llms.txt mirror Accepted 2026-07-30
0003 Capture leads through an MCP tool and an OpenAPI action, not a web form alone Accepted 2026-07-30
0004 One outbound CRM webhook to Apps Script / Sheets, not a hosted CRM Accepted 2026-07-30
0005 Productised three-tier GEO packages versus per-engagement custom scoping Proposed ⚠ 2026-07-30
0006 Target four high-CAC UAE verticals for GEO outreach Accepted 2026-07-30
0007 Dogfood jsglobtech.com as the live demo asset Accepted 2026-07-30
0008 Multi-tenant lead routing and API rate limiting Accepted 2026-07-30

0001–0007 were recorded on 2026-07-30 while seeding the knowledge base from ../source/JSGlobtech_GEO_Agency_Playbook.pdf. They document decisions made earlier; the dates are when they were written down. Where the repository already implements the decision it is marked Accepted.

⚠ ADR-0005 is unresolved and needs an owner decision. The playbook's pricing tiers contradict the published public/llms.txt. Read it before quoting anyone.