Skip to evidence
Makemake View Companion

Public engineering register · 24 August 2026

Engineering evidence,
not promises.

Makemake publishes what is released, what is implemented behind a gate, and what remains in development. Every claim below includes a scope, a verification basis and a limitation.

Read the verification Download evidence JSON

Maturity ledger

A clear line between
today and tomorrow.

Released

Public Companion presentation

The nature-led website and Google identity surface are deployed. The public presentation marks unreleased products as in development.

Open the released presentation
Implemented · gated

Identity and access controls

Phone identity code exists in source but awaits Firebase SMS configuration. Paid-entitlement evaluation awaits an authoritative ADAR projection. Private operations controls exist in the reviewed source; this public register does not assert their current deployment state.

In development

Cross-device coordination

PC, Robot, TV, Drone, IoT, Mobile and Car are planned endpoints. Makemake does not claim that these integrations or cross-device task execution are available today.

Reviewed baseline

A dated, self-reported
release check.

Source revision
1e775bbe756cb93bf0136526753657efa4b95e86
Verified
24 August 2026
Environment
Windows release workspace
Command
pnpm run check
Outcome
Passed

This command runs provider policy, secret scanning, hosting policy, TypeScript checks, automated tests and production builds. The source repository is private, so this record is not publicly reproducible. It is self-reported release evidence—not an independent certification or a real-world device benchmark.

14Web tests
11Core tests
31API tests
19Worker tests
75Total automated test cases passed in the dated Windows verification

Two worker cases are Windows-conditional. The 75-case result above refers specifically to the dated Windows run, not every CI operating system.

Implemented controls

Specific mechanisms.
Bounded claims.

  1. 01

    Paid access fails closed

    A role alone cannot unlock Companion. The reviewed presentation gate requires the exact Companion role plus a signed entitlement start and unexpired end time. Missing, malformed, future or expired claims are denied. No customer action API is represented as released.

    Implemented · tested
  2. 02

    Private operations have a separate owner boundary

    The owner identity must match the configured fingerprint, have a verified email and use Google as the token sign-in provider. Public members do not gain operational API access.

    Implemented · tested
  3. 03

    Commerce authority stays with ADAR

    Makemake does not invent a product, price or payment role. Checkout links are accepted only over HTTPS on adar.asia or its subdomains, and ordinary paid access remains closed until a signed per-user entitlement exists.

    Implemented · gated
  4. 04

    Operational AI cannot publish directly

    The reviewed operational pipeline binds proposals and images to hashes, requires local approval and fresh commerce authorization, then records a durable receipt before acknowledgement. Changed content invalidates approval.

    Implemented · deployment not asserted
  5. 05

    Credentials and work are bounded

    Secret envelopes use authenticated encryption and ownership binding. Signed worker requests include body hashes and replay windows. A worker receives one leased task credential in memory rather than the vault.

    Implemented · tested
  6. 06

    Web delivery is policy checked

    The hosting policy requires a restrictive content security policy, blocks framing and object execution, excludes unsafe inline and evaluated scripts, and exposes only the dependencies required for identity.

    Released · checked

Method

How a claim earns
a place here.

1

State it narrowly

Name the mechanism and scope. Avoid “best,” “leading,” or universal safety language without comparative independent evidence.

2

Tie it to a revision

Record the source revision, verification date, environment and exact command.

3

Show the failure boundary

Publish what the control denies, what remains gated, and what has not been measured.

4

Update or retire it

Future releases must refresh the evidence record rather than inherit an outdated claim.

Limits and next evidence

What we do
not claim.

Makemake has not published cross-device completion rates, latency or uptime measurements, independent penetration-test results, accessibility certification, customer adoption metrics, or comparative rankings. Phone joining, paid checkout and customer Companion actions are not presented as live.

The next evidence milestone is a versioned cross-device task protocol with predefined tasks, environment details, repeated runs, failures, raw results and independently reviewable methodology. Until then, device coordination remains a product direction—not proof of market leadership.

Read the machine-readable limitations