★ Now open Challenge № 001 — The Business Facts & Booking API★ Free to take No permission slip required★ New Challenge № 002 — Every published phone number must ring★ Brief filed № 004 Geographic Group Bubbles, sent to Telegram★ Brief filed № 005 Voice, Finished For You, sent to Telegram★ Brief filed № 006 One-Tap Consent — End the Gate Maze, sent to Apple & Zenodo★ Just boarded № 007–014 — AURA, COMMS, the Marketplace Agent API, Dojo & more★ Just boarded № 015 The Holographic Pair — time-synced dual-camera truth★ Rule Credit the source. Ship the thing.
An open board of public works · Est. October 22, 2026
Presidential Challenges
Big, obvious problems — posted as open challenges for anyone to build.
The ideas are published, not patented. Pick one up and start working on it.
Issued by Bryan A RiveraPosted from Miami, Florida15 challenges on the board0 permission slips required
★ ★ ★ ★ ★ ★
How this board works
1
Take any challengeEvery challenge here is free to take — no fee, no application, no asking. If it’s posted, it’s yours to build.
2
Build it in the openAlone, with a team, inside a company, as a weekend project. Prototype first; polish later. A working small version beats a perfect plan.
3
Credit the source, keep the creditThe idea came from Bryan A Rivera — say so once, somewhere visible. Everything you build is yours.
The Board
★ Flagship challenge · Filed with the FTC & Florida AG as a policy proposal
CHALLENGE № 001Spec ready — open
The Business Facts & Booking API
One free, open standard so any person — or any AI agent working for a person — can ask a business the basic questions and get a straight answer.
The problem
The most basic facts about a business — is it still there, is it open right now, what are the
happy hour specials, can I book a table — are locked behind phone tag. Published numbers ring
dead lines. Published emails bounce. Phone trees are built to make you give up. A human calling
ahead to confirm a restaurant is open is doing useful work; an AI agent calling on that
person’s behalf gets hung up on for how its voice sounds. Neither should be necessary
for facts a business could simply publish once, in a format machines can read.
The build
Design and ship an open standard — a small set of endpoints any business can publish at a
well-known address (for example, theirdomain.com/.well-known/business) —
plus a free reference implementation a one-person shop can turn on in an afternoon.
Endpoint
Answers
Notes
GET/facts
Name, address, hours, open right now, still in business
The five facts nobody should have to phone for
GET/contact
A phone number and email that actually reach the business
Verified working — see Challenge № 002
GET/specials
Today’s specials, happy hour, closures, changes
Timestamped, so agents know it’s current
POST/reservations
Book, change, or cancel a reservation or appointment
Returns a real confirmation code
GET/services
What the business offers, prices where public, accessibility info
Plain structured data — JSON is fine
The policy pair
Safe harbor: a business that publishes a working API has done its part — agents query the API instead of calling, and the business is protected from agent call volume.
No API, no hang-up: where no API exists, an AI voice calling briefly and politely on a person’s behalf must be treated like the person calling. Hanging up on the voice is refusing the person behind it — for a disabled caller who speaks through AI, that is discrimination.
Not spam: a short, purposeful call — confirm the business is open, check a special, book the table — is the opposite of spam. The standard should say so, in writing.
What “done” looks like
A published spec anyone can implement, one free open-source reference server, and the first ten real businesses live on it — a diner, a barber, a repair shop — answering machines and people alike.
If a business prints a phone number, it should ring. If it prints an email, it should land. Build the checker that proves it — in public.
The problem
Companies publish contact cards that lead nowhere: numbers that never ring a real place,
inboxes nobody reads, complaint pages that return 404. Each dead end burns the
customer’s time and quietly teaches people to give up — which is the point of the
design. There is currently no penalty for a fake door, so the doors keep getting faker.
The build
An open contact-integrity checker: feed it a business’s published phone and email; it verifies — on a schedule — that the number rings a real business line and the inbox accepts and routes mail.
A public scorecard: working, degraded, or dead — with the test history shown, so a company can fix its listing and prove it.
A model rule, ready for a legislature to pick up: a published contact that doesn’t reach the business is a deceptive practice, with a real penalty and a simple cure — publish one that works, or publish the API from Challenge № 001.
What “done” looks like
The checker running against the 100 largest consumer companies in America, results public, and one state or federal bill using its definitions.
Until every business has the API, somebody still has to make the call. Build the agent that makes it well.
The problem
Calling ahead is real work: confirm the shop is still there and open, ask about today’s
specials, hold a table, verify a repair is ready. People who communicate through AI voice —
including disabled people — are entitled to have that work done by their agent, and businesses
are entitled to a caller that is brief, honest, and easy to deal with. Right now neither side
has a standard to point to.
The build
A voice agent that identifies itself, states its errand in one sentence, asks only what it came to ask, and is done in under a minute.
An open code of conduct for agent calls: no bulk dialing, no deception, immediate respect for “use our website instead” — and a published preference signal businesses can set (a spoken-line equivalent of the API in Challenge № 001).
Accessibility first: the agent speaks for its person, in their words, and a hang-up on the agent is logged as a refusal of the person.
What “done” looks like
One open-source agent placing real, successful errand calls — reservation confirmed, hours verified — with the code of conduct published beside it.
Your people, sorted by where on Earth they are. A map of your contacts, grouped city by city — and the fastest way to start the conversation.
The idea
Open a “People by Location” view in a messaging app and your contacts gather into
bubbles on a map — one per city. Tap a city and it zooms in to the people there. You met
someone from New York last night? She’s in the New York bubble, not buried in an
alphabetical list you’ll never scroll.
The build
Tap one person’s icon → you’re in a one-to-one chat with them. Boom.
Tap several icons → you’re in a group chat with exactly those people — a group assembled off the map, by city, in seconds.
Privacy is the foundation, not a setting: nobody appears on anyone’s map without opting in, and location means city, never a live pin.
Start with the MVP — bubbles, zoom, tap-to-chat. The interface gets refined with real users after it exists.
What “done” looks like
A working prototype in any messaging app — or a standalone demo — where a city bubble becomes a group chat in two taps.
Press play once. Say you’re done, and it’s sent. Voice controls that finish themselves — no second press, no dead takes, no hunting for the button.
The problem
In the author’s own words: “When I hit the play button I don’t want to hit it
again to stop the message.” Voice today makes the user work twice for everything: press
to play, press again to stop; make one mistake or pause in silence and the take is dead; hunt
for a send button when your mouth already said you’re finished.
The build — five concepts
Auto-Cutoff Playback. Press play once. The message plays to its end and stops itself — a voice message is a fixed length, not a faucet.
Resume Where You Left Off. A pause, a silence, or a mistake mid-recording does not kill the take. Pick the conversation back up at the exact point you stopped — same message, no restart, no lost thought.
Trigger-Word Send. Sentence-final trigger phrases ARE the send button: “go,” “do that,” “we’re done here,” “send it.” When the words at the end of the sentence plainly end the sentence, the app ends and sends the message — hands stay free.
The Easy Send Button. For everyone who does want the button: one big, obvious finish-and-send target — the AURA principle (one tap = arrival) applied to voice.
Hide the Um. Transcription cleans itself: “um,” “uh,” and dead air are trimmed automatically from the text (and optionally the audio). The meaning ships; the ums don’t.
What “done” looks like
A voice interface where the sentence already knows when it’s over: playback stops itself, dictation resumes after any pause, and saying you’re done IS sending — in any voice-first app.
End the gate maze: every consequential confirmation completable as ONE tap, where the user already is — Accept / Deny, never a scavenger hunt across apps and inboxes.
The problem
One day — October 23, 2026 — in the author’s own record: a federal consumer portal
rejected three passwords against rules disclosed only after each failure, then blocked
pasting into its password field; a Google sign-in demanded a phone prompt that never
arrived; a Facebook post sat stranded behind a two-factor wall; a Zenodo account waited
unconfirmed on an emailed link. No single gate is unreasonable. Stacked, they are a
wall — and the wall falls hardest on disabled users, single-device users, and anyone
whose memory or motor control makes re-typing long secrets a genuine barrier.
The build — five demands
Confirmations are actions, not scavenger hunts. Email verification, sign-in approval, consent, and account confirmation presented as a signed, single Accept / Deny action inside the user’s existing session or agent interface — never a link buried in another app’s inbox.
Never block paste in credential fields. Paste-blocking punishes password-manager users and assistive-technology users — the exact people doing security correctly.
Password rules up front, one standard. State the full rule before the first keystroke; accept the first compliant password; never silently diverge between what was set and what is stored.
Recovery must not hinge on one prompt arriving. A sign-in prompt that never reaches the device is a lockout, not a security feature. Offer parallel paths of equal strength.
An authorized-agent channel. A user’s designated agent carries every step of a flow except the single human consent tap — no arbitrary mid-flow walls.
What “done” looks like
A disabled user, on one phone, with no second device, completes account confirmation, a password reset, a two-factor approval, and a government complaint filing — start to finish — with no more than one deliberate tap per gate and zero cross-app hunts. Any flow that fails that test is not secure; it is merely closed.
One tap = arrival. Saying it is the same door. If an action takes more than one tap or one sentence, the interface is broken — not the user.
The problem
Every app buries its actions in menus, trees, and intermediate pages whose only job is to offer another page. For disabled users the cost is decisive: hunting is the barrier, and the hunt is treated as the user's failure instead of the design's.
The build
One tap = arrival. Every destination or action gets ONE button that goes straight there — no menus, no trees, no hunting.
Voice is the same door. Saying the thing does exactly what tapping its button does — same destinations, same actions, no separate voice mode.
Buttons say what they do in plain words, and carry the person the whole way.
What “done” looks like
A phone where every action you use is one tap or one sentence away — for everyone, decisive for disabled users.
One private hub for a small core team — a closed circle with a door the members control, and alerts that cut through like a tower talking to its own crew.
The problem
Core teams drown across five channels all pinging at once, on platforms built for public feeds and stranger discovery. There is no small, governed, private room with priority alerting — so the people who matter most get the same noise as everyone else.
The build
A single hub: quick chats, picture uploads, files — one place the core team goes.
Admission by the circle: members join slowly, by invitation and member approval — and can be voted out. The circle governs itself.
Priority alerts: messages inside the circle cut through the noise; outside channels stay outside.
Private link invites: revocable, unlisted — no public discovery, no drive-by pings.
Plus: let users rename apps on their own devices — the home-screen label belongs to the owner.
What “done” looks like
A closed, member-governed circle with priority alerts, shipped inside the stack people already carry (Messages + iCloud + Focus).
Let people sell through their own AI: a seller-side API so a person's authorized agent can list, manage, and answer buyers — the same way the person would by hand.
The problem
A seller's agent cannot reply to a buyer, manage a listing, or close a sale, because marketplaces offer no agent API at all — every action must be tapped by hand inside one app, per platform, per listing. The result is dead deals and stale listings; for disabled sellers, 'just tap through five apps' is a lockout, not a workflow.
The build
A published Seller Agent API on every marketplace above a de-minimis size: list, edit, delist, message buyers, accept offers — scoped to the seller's own account.
OAuth-style delegation: the seller grants a revocable token; every agent action is signed, logged, and attributable.
Equal treatment: any action a human may take in the app may be taken by their authorized agent — no second-class listings.
Government convenes: the FTC and state AGs host the standard-setting; blocking authorized agents becomes the unfair-practice question.
Safe harbor for platforms that implement the standard in good faith.
What “done” looks like
A dynamic market where listings update themselves and replies arrive in seconds — and a sale through an AI is simply a sale.
CHALLENGE № 010Filed with Miami-Dade Transit + Apple
Digitize the EASY Card — With Fare Priority
Miami-Dade's transit card belongs in the phone — and when a rider taps, the free pass must spend before the cash does. Always, in that order, never silently.
The problem
Miami-Dade transit runs on the physical EASY Card. Lose it and you lose the system for about a week — and riders do not have a week. Every other card in a rider's life already lives in their phone; the EASY Card is the one that cannot.
The build
NFC digitization: tap the physical card once to provision it to the phone; the account, passes, and balance live on the account, not the plastic — a lost card or phone re-issues in minutes.
Fare-priority order (the core spec): first the free/unlimited/benefit fare whenever one is valid; only if no free fare applies, the cash balance.
Confirmation gate: if a tap would charge cash, the rider confirms first — 'Your free pass didn't cover this ride. Charge your cash balance?' Never a silent cash charge.
Authorization to build: the city, county, and state give the agency and its developers the explicit go-ahead.
What “done” looks like
A rider taps their phone, the free fare spends first, cash is never touched silently, and a lost card stops being a crisis.
Flip the workflow: take ONE shot, then slide between every spectral view of that same shot — and let the pictures live in the normal photo library like every other camera's.
The problem
Ghost Camera makes the user pick a filter first, then shoot — one filter per shot, so the moment must be re-lived for every spectrum. Worse, its captures stay trapped inside the app: they never reach Apple Photos or the normal share flow into apps like Telegram.
The build
Capture once; store the full frame.
One spectral slider scrubs continuously through every view of that capture — normal, UV-look, ecto, thermal-look, night, SLS overlay — blending, not hard-cutting.
Works on photos and paused video frames; export any slider position as its own image.
End the silo: captures save into the standard photo library and share through the normal picker, like every other camera app.
What “done” looks like
One capture, every spectrum, one slider — and the picture behaves like a picture everywhere else on the phone.
The fold is not just a bigger screen — it is two surfaces with a relationship. Six concepts that give the crease a grammar: canvas/notes, controls/display, people/conversation.
The problem
The first foldable iPhone ships two halves with no shared language. Apps split by accident instead of by design — a bigger screen, when what the hardware offers is a working relationship between two surfaces.
The build
Notability Fold: sketch canvas on one half, project notes on the other — a project stays in one notebook end-to-end.
Studio Fold: mixer on one half, the live waveform on the other — adjust on the left, watch the audio answer on the right.
COMMS Split: the closed circle unfolded — member list on one half, the live conversation on the other.
Dojo Fold: live map on one half, sensor readouts on the other — sensing at a glance, a pocket instrument.
Claim Cam: front and rear cameras recording simultaneously, timestamped, in one file — evidence-grade dual capture.
AURA Crease Button: one large target spanning the fold — tap anywhere on it and you arrive.
What “done” looks like
A fold with a grammar: any app can declare its two halves' jobs, and the Duo becomes a working instrument instead of a wide phone.
Assistants on different platforms should work together directly — with the user's consent — instead of forcing the user to relay messages between AIs by hand.
The problem
A person running multi-platform operations is forced to be the courier between their own AI assistants: copying outputs from one, pasting them into another, re-explaining context at every hop. The machines can talk; the platforms simply haven't opened the door.
The build
Permissioned interop: an API, shared workspace, or agent-to-agent protocol for consented cross-platform collaboration.
Shared task handoffs: one assistant passes a task — with its context — to another, under the user's direction.
Cross-checked research: assistants verify each other's work before it reaches the user.
Consent is the foundation: the user authorizes every connection; nothing collaborates behind their back.
What “done” looks like
The user directs; the assistants coordinate. No human courier between machines.
CHALLENGE № 014Published on Zenodo · DOI 10.5281/zenodo.23601720
Dojo — Tomographic Traffic Sensing
See traffic the way a CT scanner sees a body: reconstruct the whole flow field of a city from sparse sensor projections — including the streets with no sensors at all.
The problem
Urban traffic state is estimated from sparse, mismatched sensors — loop detectors, cameras, probe vehicles — and between sensors the system is blind. Routing runs on interpolated guesses, so congestion is detected late and routed around poorly.
The build
Every sensor is a projection ray: loop counts, camera lines, bus GPS pings, phone probes — each one a single projection through the city's traffic field.
Tomographic inversion: filtered back-projection or iterative sparse-view reconstruction over the projection set.
A dense, real-time congestion field across the whole road network — including segments with no sensors.
Routing on the reconstruction, not on guesses between dots.
What “done” looks like
A city that can see its whole traffic field at once — published openly as ARAANI HYPER SYSTEMS Concept Note № 7, DOI 10.5281/zenodo.23601720.
CHALLENGE № 015Open challenge · dictated Oct 23, 2026
The Holographic Pair — Time-Synced Dual-Camera Truth
Two cameras. One instant. A timecode on each phone, both locked to the same GPS satellite clock and fix — a triangle in time and space that confirms an image is real.
The problem
Any single photo can be faked, generated, or re-dated — one camera, one file, no witnesses. In a world of synthetic images, a lone picture proves nothing about where it was taken, when, or whether the scene ever existed at all.
The build
Two cameras shoot the same scene at the same instant — two phones, one moment, two viewpoints: a true stereo pair, with the parallax depth a hologram is built from.
A timecode rides on both captures — each phone stamps its frame with the same synchronized time, locked to GPS satellite time, not the phone's editable clock.
Linked in space as well as time: each capture carries its GPS position, so the two viewpoints and the satellite fix form a triangle — camera, camera, satellite — whose geometry has to agree.
The triangle is the authentication: two independent viewpoints, one shared satellite-locked instant, positions that must triangulate. Faking one image is easy; faking a consistent triangle after the fact is not.
The output is a verifiable pair: both frames, both timecodes, both fixes, and the math that checks them — proof a real place stood in front of two real cameras at a real moment.
What “done” looks like
Point two phones at a scene, and the pair itself certifies the shot: this happened, here, at this time — no trust-me required.
No challenges in this category yet — post the next one.
Builders & credits
Every Challenge is issued by Bryan A Rivera · ARAANI HYPER SYSTEMS. Builders keep
everything they build — the one rule is attribution. Cite it like this:
“Presidential Challenge № 00X — [Title], by Bryan A Rivera (ARAANI HYPER SYSTEMS),
presidential-challenges.pages.dev” — and file your build through the
“I built this” button on the Challenge. Reported builds land on this wall.
🧱
The wall is openNo builds reported yet. Ship any Challenge, file the report, and your name + link go here — first spot is forever first.
🏆
Bounties pay on proofThe first reported, working build of a Challenge takes its tip-pool bounty. Proof = a live link or demo anyone can open.
✍️
Commission a ChallengeGot a gate maze of your own? A $25 tip gets your Presidential Challenge written and posted to this board, credited to you as the commissioner.
Support the board
The blueprints on this board are free to take — published openly, on purpose.
Tips keep them coming, and tips pool into a builder bounty for each Challenge:
the first builder who ships a Challenge and credits the source takes its bounty.
⚡
Tip the blueprint — Krak (main rail)krak.app/@starshipdev — the fast lane. Tips land here first: no collections, no funny business.
💸
Tip the blueprint — Cash App$bryyaan — also accepted. Tips keep the board running and the Challenges coming.
🏆
Fund the buildEvery tip pools into the bounty for the newest Challenge. Build it first, credit the source (Bryan A Rivera), and the bounty is yours.