Syntax Space Studio

Syntax Suite

Eight platforms, one lineage.
And a studio that builds on them.

Every platform after the first was extracted, forked, split or ported from one before it, or is to be. Select one to see where it came from, how far along it is, and where Claude stands in it.

syntax-suite · ecosystemselect a platform

gen 0 · the core

gen 1

gen 2

gen 3

AEP

AI Experience Platform

In use · guest chat built and graded

claude: guest chat built and graded · staff drawer on for no business yet

The customer-facing platform: websites, bookings, storefronts and chat, one deployment per business.

For
Businesses that serve customers directly: resorts, restaurants, courts, spas and shops.
Status
Six businesses provisioned
  • ABP extracted from AEP ABP was built by extracting the proven parts of AEP into a generic, brandable suite.
  • ACP ported from AEP ACP is a new codebase on AEP's pattern, with AEP's foundations ported into it.
  • ALP extracted from AEP ALP ports AEP's proven modules file by file, never as a fork.
  • ASP to be ported from AEP ASP is to port AEP's proven modules into its own codebase, never extending AEP; none is ported yet.

See AEP at work

ABP

AI Business Platform

Built · AI layer proposed

claude: Claude planned

The white-label back office: CRM, employees, assets, vendors, quotes and invoicing, module-gated and themed per client and sold under the client's name.

For
Any business that wants its back office under its own brand.
Status
Built; its first client deployment is being stood up

Extracted from AEP

  • ABP extracted from AEP ABP was built by extracting the proven parts of AEP into a generic, brandable suite.
  • ALP ported from ABP ALP takes ABP's hardened platform layer by shape, rewritten for its own codebase.
  • AREP forked from ABP AREP is a fork of ABP with full history, and keeps merging from it.
  • Custom built on ABP The vendor payment system is ABP's vendor-management module and vendor portal, configured for one client.

See ABP at work

ACP

AI Content Platform

In build · in-product writer planned

claude: Claude planned

The content, scraping and ranking engine behind a portfolio of .ai domains: city guides, ranking sites and data sites, from one config-driven codebase.

For
Readers of its own sites.
Status
The queue is built, not deployed; entries are written by Claude agents in the studio

Ported from AEP

  • ACP ported from AEP ACP is a new codebase on AEP's pattern, with AEP's foundations ported into it.
  • AIP forked from ACP AIP took ACP's planning system and code foundation, not its product.

See ACP at work

ASP

AI School Platform

Planned · AI planned, model not named

claude: AI layer planned, model not named

A school management suite where the student information system and the learning platform are one product: attendance, grades, fees, curriculum and parent communication on one record, one branded deployment per school.

For
A school and the people around it: registrar, teachers, guardians and students.
Status
Planned: the plan and tracker are done; the code scaffold is next

To be ported from AEP

  • ASP to be ported from AEP ASP is to port AEP's proven modules into its own codebase, never extending AEP; none is ported yet.

See ASP at work

AREP

AI Real Estate Platform (working name)

In build · no AI planned

claude: no AI layer planned

White-label property management: agencies run buildings, leases, tenants and repairs; owners see what their units earn; tenants pay rent and raise repairs in a branded portal.

For
Realtors, property managers and landlords, and the tenants and owners they answer to.
Status
In build; a demo runs on sample data; no client deployment yet

Forked from ABP, 30 Aug 2026

  • AREP forked from ABP AREP is a fork of ABP with full history, and keeps merging from it.
  • ALP a proposed feed from AREP A proposed read-only owner feed: what AREP's owner portal shows an owner lands in that owner's ALP household ledger.

See AREP at work

Custom-made

Vendor Payment Management System

Built

A supplier submits an invoice through its own portal; it moves through the client's approval chain, is paid, and closes only when the supplier's official receipt is verified.

For
A client's finance team and the suppliers it pays. The client is not named.
Status
Built. Its first deployment is being stood up.
  • CUSTOM built on ABP The vendor payment system is ABP's vendor-management module and vendor portal, configured for one client.

More on custom work

ALP

AI Life Platform

Foundations built · AI planned

claude: Claude planned

A private household portal: the day, the kitchen, the people who help run the home, the money going out and the things in it.

For
A household and the people who help run it.
Status
Foundations built; the life-ops core is next

Extracted from AEP · ported from ABP

  • ALP extracted from AEP ALP ports AEP's proven modules file by file, never as a fork.
  • ALP ported from ABP ALP takes ABP's hardened platform layer by shape, rewritten for its own codebase.
  • AHP split from ALP AHP split out of ALP so health data lives in a product built for it; the two share no data.
  • ALP a proposed feed from AREP A proposed read-only owner feed: what AREP's owner portal shows an owner lands in that owner's ALP household ledger.

See ALP at work

AIP

AI Investor Platform

Planned · Claude planned

claude: Claude planned

Engagement intelligence for Canadian and US small caps: it catches the release where a company hires a marketing or investor-relations firm, follows the stock for two months, and ranks the firms by outcome.

For
One client deployment, watching every publicly listed company on the Canadian exchanges and the US markets, roughly 8,000 issuers.
Status
A commissioned build for one client, on the shared foundation

Forked from ACP, 13 Sept 2026

  • AIP forked from ACP AIP took ACP's planning system and code foundation, not its product.

See AIP at work

AHP

AI Health Platform

Built, not deployed · AI planned

claude: Claude planned

A private family health suite: profiles and the care circle, medications with caregiver escalation, vitals and an encrypted records vault.

For
A family and its care circle.
Status
Health MVP built and tested; not yet deployed

Split from ALP, 3 Oct 2026

  • AHP split from ALP AHP split out of ALP so health data lives in a product built for it; the two share no data.

See AHP at work

extracted, forked, split, ported or built on to be ported, or a proposed feed

Each platform at work

In the order of how far each one has got. Each screen plays its moment beside the same moment in plain words; a person makes the decision in every one.

AEP · AI Experience Platform

Claude checks the courts and the business prices the slot. The guest confirms.

Businesses that serve customers directly: resorts, restaurants, courts, spas and shops.

AEP · AI Experience Platform

In use · guest chat built and graded
  1. 1

    Guest asks for the 6pm court, paying by GCash

  2. 2

    Claude asks the business for a price

    sports_quote_court

  3. 3

    The business prices it from its own rates, on the card

    the price is on the card, never in the reply · graded (sports-002)

  4. 4

    Guest confirms

    no confirm button: the guest confirms by typing

  5. 5

    Claude holds the court against that quote

    sports_reserve_court · needs a fresh quote (sports-004)

  6. 6

    The guest’s phone shows a held court, and how to pay

A guest’s phone in AEP, drawn from the product · amounts from the eval suite, shown without a currency · sample records · reply wording illustrative

AEP · AI Experience Platform

One guest, one conversation, across the business’s modules.

Businesses that serve customers directly: resorts, restaurants, courts, spas and shops.

AEP · AI Experience Platform

Built and graded · hotel set up for no business yet
  1. 1

    Guest asks for towels, in the chat that holds the booking

    concierge_create_request · graded (pms-009)

  2. 2

    Claude → housekeeping files the request against the guest’s stay

    the stay is matched to the guest, never to a room number typed in chat

  3. 3

    Guest asks to check out late, the fee on the bill

  4. 4

    Claude → the front desk passes it on; a person decides, and nothing is charged in chat

    concierge_request_late_checkout · no charge written · graded (pms-006)

A hotel guest’s chat on Messenger, as the channel prints it today, the card as plain lines, reference and payee left out · three separately graded turns shown in one thread, sequence illustrative · the model’s lines are the evals’ scripts; the evals grade what the platform does with them · sample records, amounts without a currency · hotel and concierge built and graded, set up for no business yet

ABP · AI Business Platform

A supplier sends an invoice. The client’s approvers sign it off, in order.

Any business that wants its back office under its own brand.

ABP · AI Business Platform

Built · AI layer proposedBuilt; its first client deployment is being stood up
  1. 1

    Supplier sends the invoice from a phone, under the client’s name

  2. 2

    Finance sees it arrive

    tenant key, then AP, then a number; a repeated invoice number is refused

  3. 3

    Finance opens it; the chain runs in order

  4. 4

    Finance approves its stage

  5. 5

    Supplier sees one word at every stage: Being reviewed

The supplier’s phone and the approver’s dashboard in ABP, drawn from the product · sample records, amounts without a currency

AHP · AI Health Platform

A missed dose is never silent. One tap from a caregiver stops the alerts.

A family and its care circle.

AHP · AI Health Platform

Built, not deployed · AI plannedHealth MVP built and tested; not yet deployed
  1. 1

    The app reminds the caregiver at 8:00

  2. 2

    Nobody answers so the ladder escalates to SMS, a required step

  3. 3

    Caregiver opens Check in

  4. 4

    Caregiver one tap, and the alerts stop

    the escalation stops — plan wording, household-app-pwa.md

A caregiver’s phone in AHP, drawn from the product, not yet deployed · sample records

AREP · AI Real Estate Platform (working name)

A tenant reports a repair. The office reads it and judges what it needs.

Realtors, property managers and landlords, and the tenants and owners they answer to.

AREP · AI Real Estate Platform (working name)

In build · no AI plannedIn build; a demo runs on sample data; no client deployment yet
  1. 1

    Tenant reports it from a phone

  2. 2

    The office sees it in the open queue

  3. 3

    The office opens it

  4. 4

    The office reads it and judges what it needs

  5. 5

    Tenant is told, in plain words

The tenant’s phone and the office’s dashboard in AREP, drawn from the build, October 2026 · sample records

ACP · AI Content Platform

Claude agents write the guide in the studio. A person approves each page, and the page says so.

Readers of its own sites.

ACP · AI Content Platform

In build · in-product writer plannedThe queue is built, not deployed; entries are written by Claude agents in the studio
  1. 1

    Claude agents, in the studio researched, wrote and fact-checked the entry, citing each source

    Stage A: written with Claude Code outside the product; the in-product writer is planned (phase 3)

  2. 2

    A reviewer approves it, labelled as AI-written

  3. 3

    The queue moves to the next item

  4. 4

    A reader sees the page, with the label that says who wrote it

The reviewer’s backoffice and a reader’s phone in ACP, drawn from the build, October 2026 · the queue is built and not yet deployed · sample records

ALP · AI Life Platform

Planned: dinner from what is in the pantry. Nothing is saved until someone taps Accept.

A household and the people who help run it.

ALP · AI Life Platform

Foundations built · AI plannedFoundations built; the life-ops core is next
  1. 1

    The household sees what it can cook now, expiring things first

  2. 2

    AI · planned drafts the week from what is in stock, and saves nothing

    “what should we cook this week?” · the model picks and orders, it never invents a recipe

  3. 3

    The owner taps Accept

  4. 4

    The cook gets a list that says why each thing is on it

A household phone in ALP: Today drawn from the build; the kitchen screens drawn from its plan · illustrative · sample records

AIP · AI Investor Platform

Planned: Claude reads each release and quotes its evidence. Only what a reviewer approves counts.

One client deployment, watching every publicly listed company on the Canadian exchanges and the US markets, roughly 8,000 issuers.

AIP · AI Investor Platform

Planned · Claude plannedA commissioned build for one client, on the shared foundation
  1. 1

    AI · planned flags a release that names an engagement

    keyword pre-filter → Haiku 4.5 classifies

  2. 2

    AI · planned extracts the facts

    Sonnet 5 extracts; fenced payload; confidence and model shown

  3. 3

    The evidence a quoted sentence behind every field

  4. 4

    A reviewer approves; only an approved row counts

  5. 5

    The client gets evidence, not advice

    alerts are built from reviewed rows; no model-authored text

AIP’s review queue, drawn from its plan · illustrative · sample records · not investment advice

ASP · AI School Platform

Planned: AI drafts the feedback. The teacher approves the grade.

A school and the people around it: registrar, teachers, guardians and students.

ASP · AI School Platform

Planned · AI planned, model not namedPlanned: the plan and tracker are done; the code scaffold is next
  1. 1

    AI · planned drafts feedback against the rubric

  2. 2

    Teacher reads the draft

  3. 3

    Teacher changes what they disagree with

  4. 4

    Teacher approves the grade

  5. 5

    Guardian sees it, with no sync step

    assignment → gradebook → report card → parent portal (plan)

A teacher’s screen and a guardian’s phone in ASP, drawn from its plan · illustrative · sample records

AEP · AI Experience Platform

AEP: one core, many kinds of business

Switch on the modules a business runs. They write to one guest record, and the outlets settle on one open tab or one room folio.

aep · modulespick a kind of business
  • Customersalways on
  • Financealways on
  • Employeesalways on
  • Analyticsalways on
  • Hotelbuilt and tested, in no business’s setup yet
  • Resort bookingsin one business’s setup
  • Restaurantin several businesses’ setup
  • Spabuilt and tested, in no business’s setup yet
  • Eventsin several businesses’ setup
  • Retailin several businesses’ setup
  • Accountsin several businesses’ setup
  • Sportsin one business’s setup
  • Rentalin one business’s setup
  • Consignmentin one business’s setup
  • Campaignsin several businesses’ setup
  • Photoboothbuilt and tested, in no business’s setup yet

One guest record; the restaurant and the shop bill to the room folio; tips and therapist fees in one payroll.

One member record and its waivers; one open tab; facilitator fees in payroll; tournament events.

Recipes draw down stock; margins per item; tips to servers; segments by restaurant activity.

Outlet sales tagged to the event roll up as its attributed revenue; event staff pay.

One record, one open tab and folio, one loyalty balance, one payroll and one set of books.

always on, or in several setups in one setup in no setup yet Read from the seven setup files on the core, the defaults each business starts with; staff can switch a module in its settings. Not usage. The combinations are illustrative, not customers.

Every outlet writes to one guest record. Staff settle the open tab in one payment.

AEP · the staff dashboard, one guest

Built and tested · part of every business’s core
  1. 1

    The record keeps what this guest spent at every outlet the business runs

    customerId on stays, orders, appointments, sales, tickets

  2. 2

    The platform gathers what is still unpaid across outlets

    open tab: sports, restaurant, retail, rental, spa

  3. 3

    Staff open one bill with every outlet’s items on it

  4. 4

    Staff record one payment for all of it

  5. 5

    The record shows nothing open; the history stays

A guest’s profile in AEP’s staff dashboard, drawn from the product · sample records, amounts without a currency · the open tab covers sports, restaurant, retail, rental, spa; a hotel stay is billed on its folio · spa is built and tested, in no business’s setup yet

  • Duplicates merge into one profile, every linked record moved, with an audit row.
  • Segments by spend and lapsed days feed SMS, email, Messenger, WhatsApp and Telegram.

The restaurant puts dinner on the guest’s room. The front desk settles one folio.

AEP · the restaurant’s bill-out, then the guest folio

Built and tested · hotel set up for no business yet
  1. 1

    Server bills out dinner on the tab instead of in cash

  2. 2

    Server finds the guest’s open folio

  3. 3

    Server puts it on the room

  4. 4

    The folio holds the stay and the outlets’ charges, each labelled by module

    account types: walk_in_tab · member_account · guest_folio · corporate

  5. 5

    The front desk will settle one balance after checkout

The restaurant’s bill-out and the guest’s folio in AEP, drawn from the product · sample records, amounts without a currency · the Module column prints raw keys, as the product does · the spa can post to a folio only through the API so far

Also from their own screens: retail, rental, sports courts, photobooth.

Where else the modules meet

  • Loyalty: eight modules, nine point sources, one balance, with bronze, silver, gold tiers and redemption.
  • Segments by spend and lapsed days feed SMS, email, Messenger, WhatsApp and Telegram.
  • The outlets post what each person earned. Payroll computes pay and tax, and a person finalizes it; paying out is done outside it. Retail commission is supported at a rate each business sets, 0% in every business’s setup today.
  • The hotel’s day close posts the night, locks the business date and records occupancy, ADR and RevPAR. The hotel is built and tested, in no business’s setup yet.
  • VAT set per module, inclusive or exclusive.
  • Senior citizen and PWD: VAT removed, then 20% off, the ID recorded.
  • Official receipts numbered OR-00001 onward.
  • BIR 1601-C and remittance references prepared for the accountant.

Custom-made

Custom work proves a module. The module joins the suite.

A supplier submits an invoice through its own portal; it moves through the client's approval chain, is paid, and closes only when the supplier's official receipt is verified.

  • Approvals run in order. No stage can be skipped, and the chain is frozen onto the request when it is submitted.
  • Every approval is signed with a one-time code from the approver's authenticator.
  • A repeated invoice number is refused by the database; a likely duplicate is flagged at submission.
  • A request can hold one payment at a time, so it cannot be paid twice.
  • A rejection or a return must say why.
  • Suppliers sign in on a separate tier with its own secrets, and see only their own requests.
  • Nothing closes without the supplier's official receipt.

Built Its first deployment is being stood up.

A client's finance team and the suppliers it pays. The client is not named. The supplier’s phone and the approver’s screen are ABP at work, above.