Products & Research

A flagship product, plus verifiable cross-brand R&D.

The site presents work in three layers: CPIN-owned products, cross-brand cases led by the core R&D lead, and the team's engineering capabilities. Each layer discloses its development role, operating entity, stage, and public-release status separately.

Three-layer disclosure

Be clear about whose work it is before describing the technology.

Cross-brand cases can demonstrate the core team's engineering depth without being presented as CPIN assets. Unconfirmed ownership, brands, screenshots, revenue, and compliance status are withheld or marked pending.

01

CPIN products and services

Products planned, developed, and operated by CPIN. AnyTaxi is the current flagship, with status and limits disclosed from public evidence.

02

Cross-brand R&D cases

Cases where the core R&D lead directed planning, design, and engineering, but a separate brand or entity operates them. Public pages cover engineering and method, not CPIN ownership.

03

Team engineering capabilities

Voice AI, platform engineering, multi-agent governance, game factories, data, and testing methods that support collaboration and SBIR execution capability.

CPIN-owned flagship

AnyTaxi smart mobility dispatch

Starting with the phone call, AnyTaxi converts inbound orders into structured records and connects them to dispatch and fleet operations. Telephony, human transfer, and the fleet back office have operating records; recognition, address parsing, dispatch, and end-to-end reconciliation remain under validation.

Pilot / field validation Public technical case
Product and verified status

Approved cross-brand case

AI multi-agent autonomous governance

Research into how multiple AI agents divide work, propose actions, review one another, and execute only with human approval. The focus is governance and traceability, not a claim of an autonomous company or unattended operations.

Research / prototype; some modules have internal dashboards. Public technical case Personal-led · ownership pending

Multi-agent governance research centred on roles, permissions, approvals, and audit, exploring controlled AI collaboration inside organisational workflows.

  • Role separation:Separate agents for research, proposal, execution, and review so one agent does not both propose and approve.
  • Human approval gates:High-risk actions require human approval; the research does not claim unattended autonomous operation.
  • Task board and audit records:Traceable records for task state, agent output, decisions, and exceptions.
  • Tool and permission boundaries:Explicit tool interfaces and permission boundaries constrain what agents can execute.
  • 3D office prototype:Hermes3D is a visualisation and interaction prototype; art and public scope are not approved.
Read the research case

Engineering capabilities

Cross-brand experience, expressed as verifiable engineering capability.

The areas below are capabilities, not a public list of unapproved products. Other cross-brand cases remain under ownership, brand, screenshot, and legal review and are not linked from this page.

01

AI systems and governance

Multi-agent roles, approval gates, task state, audit records, and human takeover; research is not autonomous operation.

02

Voice and operations platforms

Voice entry, field extraction, human review, dispatch, and fleet back office, grounded in AnyTaxi field validation.

03

High-interaction platform engineering

Engineering capability across lobbies, module lifecycles, game factories, localisation, back office, testing, and deployment; specific cases remain under public-review.

04

Research methods and data governance

Reproducible backtesting, cost models, elimination gates, and risk disclosure; no investment advice or return claims.

Unapproved interactive entertainment, AnyHook, and quantitative research cases remain on a controlled preview branch and are not merged into production.

Publication rules

Engineering work can be public without confusing ownership or stage.

Every case must answer: who led it, who operates it, who owns the IP, what stage it is at, and which screenshots and data are approved for publication.

  • Do not describe another brand's or entity's work as CPIN-owned.
  • Do not describe planning, research, or test passes as commercial operation.
  • Do not publish customer data, contracts, keys, payments, revenue share, or sensitive operating data.
  • Screenshots and brand names require public-release permission; if absent, they are omitted.
  • Gaming, payments, finance, or children's content requires legal review first.

Work with us

Need AI governance, platform engineering, or research collaboration?

Tell us the context and the intended public scope. Where other brands, screenshots, payments, or regulation are involved, we confirm ownership and review boundaries first.