⚙️ Seat Charter · AI Architecture & Technology Lead · Tier 2 · v1.0 · 🟢 Live
What this seat exists to deliver, what it is responsible for, what it may decide, and how it is measured.
Part of the REMAP Business Operating System. Approved September 2026 · Reviewed at each quarterly.
Solution quality, platform reliability, and a steady flow of internal builds that become client value.
Every engagement starts on a sound architecture; the platform holds; and the business runs on the tools it sells.
| Reports to | Integrator / COO |
| Directs | AI Architects (Solutions, Platform) · DevOps / Infrastructure Engineer · Internal Engineers · R&D Engineer · Security & Compliance Engineer (fractional) |
| Reviews | Two agent-led responsibilities 🤖: Product Manager · Internal Tool Monitoring & Deployment |
| Also in this function | The AI Strategist responsibility, currently held by the founder |
| Chairs | The Weekly Leadership Sync |
See Accountability Chart.
| Metric | Target |
|---|---|
| Platform uptime | 99.9% (internal target) |
| Critical incidents responded to within 6 hours | 100% |
| Agent-led builds shipped or updated | 1 / week |
| Client escalations to Architects | ≤ 2 / week |
| Engagements with documented solution design before build | 100% |
| Internal engineer time on internal build | ≥ 60% |
See Weekly Scorecard.
See Quarterly Priorities.
Every engagement has an Architect. The Architect:
The specialist owns the how and has the freedom to build within the design. The Architect is not the delivery manager and does not do the building.
Two Architect roles:
| Role | Focus |
|---|---|
| AI Architect (Solutions) | Client engagements and application design |
| AI Architect (Platform) | Private AI platform, infrastructure and data residency |
Architect roles are added with client load, not with demand for the title: proposed at one Solutions Architect per roughly ten active seats. Architects develop the AI Strategist capability (commercial diagnosis, roadmap) over 2027 under the founder; the Strategist title is not conferred until that capability is demonstrated.
Private AI platform on AWS: hosting for clients (included while contracted), certifications maintained, monitoring and alerting via the Internal Tool Monitoring agent. Per client: data residency, access control, backups, and clean data handover on exit, implemented and maintained by this seat; Finance & Legal defines the requirements and audits.
⚠️ Gap to close by 31 Oct: on-call arrangement, incident process and response targets, defined by the DevOps Engineer and approved by the seat holder.
The core technology roadmap: client portal (proposals, partner sign-up, project management, onboarding and offboarding flows), internal tools, and the internal task platform decision. The seat holder decides this roadmap and commits to a quarterly sprint agreement with SRS where required. The internal engineering core (capped at about three permanent members) works on internal build; that is what it is for.
Workflows and agents built and deployed internally first, so REMAP gets the benefit and can then say to clients "we just did this, do you want it?". Directed by the founder with the seat holder; built by the internal core and the R&D Engineer; fed into the weekly client value loop. Includes the agent-led responsibilities on the Accountability Chart, sequenced in the Agent Build Backlog.
Internal engineers surge into client work to help a specialist land something that matters, close out an engagement well, or deliver a surprise project for a client who is stepping down or exiting, so every client leaves as an advocate. Capped at about 40% of internal engineer time, flexed with bench availability. Requested by Client Success or the Project Manager; approved by the seat holder.
Productised builds: a client comes with a defined agent or automation; it is delivered as an in-person or live build workshop led by the founder with internal team support, then handed to a seat for maintenance and extension. A cross-sell path into embedded seats. Scoped like any client project.
The R&D Engineer coordinates internal R&D: the Agent Build Backlog, internal R&D workshops, and packaging anything the Project Manager or Architects flag as reusable from client work (anonymised). Bench and fractional specialists are drawn in for builds. Participation is the standard for every specialist; the programme produces case material for the value loop and for Marketing.
Code, documentation and deployment standards for specialists and internal engineers. Architects review specialist technical quality and run technical interviews for bench hires with the HR Recruiter. Reviews the Product Manager agent's feedback and roadmap synthesis; the seat holder makes the product decisions.
| Cadence | What happens |
|---|---|
| Weekly | Chairs the Monday sync. Scorecard lines updated before it. Platform alerts reviewed. Agent backlog progress. Surge requests decided. Architect check on every active engagement's blockers. |
| Monthly | R&D workshop held. Specialist technical quality reviews with the Project Manager. Compliance implementation checklist reviewed per client with Finance & Legal. Internal roadmap progress against the sprint agreement. |
| Quarterly | Sprint agreement for the next quarter committed as Quarterly Priorities. Architect capacity against active seats. Stack review. Product decisions from the Product Manager agent's synthesis. Seat charter reviewed. |
| Per engagement | Architect in discovery. Solution design documented before build. Kickoff with the Project Manager. Technical lead at the month 2.5 strategy review and quarterly reviews. Clean data and hosting handover at exit. |
Principle: Technical decisions are made by the people closest to the technology; anything that changes cost, client commitments, headcount or security posture is visible to the Integrator.
Approved by the founder, September 2026; reviewed quarterly.
| Action | Technology seat / role | Approval | Notes |
|---|---|---|---|
| Solution design and stack choice within the agreed stack | Architect decides | — | Documented before build starts. |
| Departure from the agreed stack, or a client-hosted deployment | Architect proposes | Seat holder decides | Data residency and support implications recorded. |
| Production change or deployment on the platform | DevOps Engineer, with review | — | Change record kept; rollback defined. |
| Granting access to client data or systems | Architect approves, logged | — | Least privilege; removed on exit. |
| Declaring a security or platform incident | Seat holder or DevOps Engineer | Integrator informed within 24 hours | Client informed per contract. |
| Internal technology roadmap and quarterly sprint agreement | Seat holder decides | Founder directs the value-creation stream | Committed as Quarterly Priorities. |
| Surge allocation of internal engineers to client work | Seat holder approves | — | Cap ~40% of internal engineer time. |
| New tools, subscriptions or infrastructure spend | Propose | Per the Finance & Legal Delegation of Authority | Mapped to the Technology seat card. |
| Adding an Architect role or changing the internal core headcount | Propose | Integrator decides | Tied to active seat count. |
| Client uptime or response commitments in contracts | Propose | Seat holder and Revenue Lead agree; Finance & Legal issues | None given today beyond six-hour critical response. |
| System | Role | Purpose |
|---|---|---|
| AWS (Private AI platform) | Admin (DevOps Engineer, Platform Architect); scoped access for others | Hosting, monitoring, backups, residency |
| n8n (automations.remap.ai) | Owner | Internal and client workflows, agents |
| Client portal codebase and hosting | Owner | Core technology direction |
| Jira | Admin | Internal sprints; client project visibility |
| GitHub / code repositories | Owner | Standards, review, deployment |
| Client systems | Per engagement, least privilege, logged | Solution delivery |
| Wise / Relay | Technology seat card only | Tools and infrastructure within the cost map |
| What fit looks like for this seat | |
|---|---|
| Understands | The difference between architecture, delivery management and building, and holds the line between them; what makes an embedded engagement technically sound from day one; how to run a small platform reliably without 24-hour cover. |
| Wants | To be measured on solution quality, reliability and shipped internal builds, and to chair the operating rhythm. |
| Capacity | The nine responsibilities above, with two Architects, DevOps, the internal core and the R&D Engineer carrying volume. The seat is accountability and direction, not the building. |
See Seat Fit Assessment.
| Responsibility | Sits with |
|---|---|
| Delivery management, client reporting and specialist day-to-day | Delivery & Client Ops |
| Commercial diagnosis and roadmap ownership with the client | AI Strategist (founder), until the capability is demonstrated |
| Defining compliance requirements and auditing them | Finance & Legal (this seat implements) |
| Selling and pricing | Revenue & Partnerships |
REMAP Business Operating System · Seat Charter: AI Architecture & Technology Lead · v1.0 · September 2026 · Internal · Reviewed at each quarterly