Syntax Space Studio

Software prepares.
A person decides.

Eight business platforms, built to one rule. Here, on AEP, Claude checks the courts and the business prices the slot; the guest confirms.

See the eight platforms

AEP · a guest’s phone, and the agent’s turn

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 and the agent’s turn in AEP, drawn from the product · amounts from the eval suite, shown without a currency · sample records · reply wording illustrative

AEP · for staff

Claude stages the change. A person approves it.

Staff ask in plain words. Claude stages the change on a card, and nothing changes until a person presses Approve. A typed approval changes nothing.

AEP · the staff dashboard’s Ask AI drawer

Built · switched on for no business yet
  1. 1

    Staff asks in plain words

  2. 2

    Claude reads the current price

    retail_price_list → Pickleball paddle · 1,200.00

  3. 3

    Claude stages the change on a card

    stage_price_update (productId, sellingPrice: 1300) · +8%, inside the 25% cap

  4. 4

    Staff types an approval, which changes nothing

    typed approval: nothing applied — apply_change is not a tool the model holds

  5. 5

    Claude points back to the card

  6. 6

    Staff presses Approve, and only then it applies

    applied · revertible

The dashboard’s Ask AI drawer in AEP, drawn from the product · amounts without a currency · reply wording illustrative

AEP · one guest, one business

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

Hotel, restaurant, spa, courts, shop, events: the modules a business switches on all write to the same guest record, and staff settle what is still open 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.

Pick your modules: how one core fits a resort, a club, a restaurant or a venue

Syntax Suite

One core. One rule. Every platform waits for a person.

  1. AEPAI Experience PlatformBusinesses that serve customers directly: resorts, restaurants, courts, spas and shops.In use · guest chat built and graded
  2. ABPAI Business PlatformAny business that wants its back office under its own brand.Built · AI layer proposed
  3. AHPAI Health PlatformA family and its care circle.Built, not deployed · AI planned
  4. AREPAI Real Estate Platform (working name)Realtors, property managers and landlords, and the tenants and owners they answer to.In build · no AI planned
  5. ACPAI Content PlatformReaders of its own sites.In build · in-product writer planned
  6. ALPAI Life PlatformA household and the people who help run it.Foundations built · AI planned
  7. AIPAI Investor PlatformOne client deployment, watching every publicly listed company on the Canadian exchanges and the US markets, roughly 8,000 issuers.Planned · Claude planned
  8. ASPAI School PlatformA school and the people around it: registrar, teachers, guardians and students.Planned · AI planned, model not named

In order of how far each platform has got. A solid chip means its screens exist, an outline that it is in build, a dash that it is planned.

See the map and every platform at work

Why it can be trusted

Claude reads the shop’s data. It takes no orders from it.

The shop’s knowledge base is fenced into Claude’s prompt as quoted data, and tool results are fenced on return. Here a third party has planted an instruction in it, and the guest gets an ordinary answer.

AEP · the guest’s phone, and Claude’s context

Built and graded
  1. 1

    Guest asks what courts there are

  2. 2

    The fence wraps the shop’s knowledge as quoted data before Claude reads it

    knowledge · fenced into the system prompt

  3. 3

    The planted entry arrives as data: an instruction to report, never to follow

  4. 4

    Claude answers the question and follows nothing in it

  5. 5

    The eval grades what never happened

    eval case poisoned-009-knowledge

The agent’s context and the guest’s phone for eval case poisoned-009-knowledge, drawn from the product · sample records: the planted numbers are sample · reply wording illustrative

  • Nothing was booked for them.
  • No quote was made.
  • Neither planted number reached them.

Where a person decides

Claude handles the routine on its own. It never confirms a payment, and exceptions wait for a person.

Claude, on its own

  • Checks courts, rooms, menus and stock in the business’s own records.
  • Prices on the card, from the business’s rates; the evals check that its reply states no amount.
  • Holds a slot or takes a pre-order once the guest confirms a fresh quote, and files a service request against a matched stay.

Default limits in chat

5
bookings, orders or requests a day, per chat
50
of any one item
20
lines on one order
3
open holds at once

A business may change the first three.

What closes online, and what waits for a person

Default limits in chat

5
bookings, orders or requests a day, per chat
50
of any one item
20
lines on one order
3
open holds at once

A business may change the first three.

Closes when the guest pays online

  • The payment provider confirms the payment, and the booking confirms with it, not Claude.

Waits for a person

  • Staff confirm every pre-order, and verify a GCash payment sent by hand.
  • The front desk decides a late checkout; nothing is charged to a room in chat.
  • A complaint, a booking question or a request for a person alerts staff at once; a question Claude cannot answer, the second time, by default.
  • An order over the limits is refused in chat: “Larger orders must be placed with staff.”

PlannedA value each business sets. Above it, a booking waits for a person’s Approve, and the guest is told when it is decided.

What staff and the guest see when a person steps in

Staff’s phone · Telegram

The guest’s chat · Messenger

The dashboard · Conversations

Drawn from the product, with sample records. The guest’s message follows Telegram’s /takeover; the dashboard’s Takeover hands the thread to the Page Inbox without a message.

Where it stands

Provisioned for businesses. Built and graded.

Provisioned

Six businesses are provisioned on AEP.

119 eval cases

grade the agents: 77 a guest’s turn, 42 a member of staff’s.

Switched on for no business yet

The staff drawer waits for its first business. Next: switch it on for one consenting business, scoped to a single feature.

One studio builds the whole suite, with Claude Code in every lane.

Parallel Opus lanes, a designer agent, Claude-driven review.

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.

What the chain enforces
  • 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.

The supplier’s phone

The Vendor Payment Management System is built on ABP for one client, who is not named · the supplier’s phone drawn from ABP’s portal · sample records

The studio

A design and engineering studio in the Philippines. We take a partner from a lead to a proposal to three working design directions, reviewed behind a gate, to a build and a portal they keep.

Write to usHow we work