Actual FS27 control plane
The public entry to the gate. Admin access, user key request, dashboard, smoke test, monitor, and platform-control surfaces live behind this project.
Open GatePublic proof surface
The gate behind deployable command decks.
SkyeGateFS27 is the control plane that lets a client website become more than a brochure. It can issue and validate access, mirror platform events, track deployment work, centralize vendor keys, and hand a business owner a command deck that feels operated instead of merely hosted.
Live proof links
Sendable surfaces, separated by audience.
Bearer introspection contract
Client apps send a bearer token server-side and receive an active/inactive identity result. No client should publish secrets or hard-code owner keys.
Open Function RoutePlatform event mirror
Deployed apps can mirror approvals, tasks, user activity, smoke tests, and operating receipts into the gate through a server-only mirror secret.
Open Event IngressMetrAIyux 0S integration
The live MetrAIyux 0S deployment uses FS27 as the auth and evidence bridge for a 16-brain autonomous business command system.
Open Full SystemArchitecture made legible
A client website can become a controlled business surface.
The public website handles attention. The command deck handles work. FS27 handles the gate: identity, event evidence, vendor posture, deployment tracking, and admin-owned controls. That separation is the product.
A public site, client portal, or proof page explains the offer and captures intent without exposing private setup instructions.
The 16-brain layer routes sales, client success, staffing, tech, compliance, proof, and founder strategy into clear next actions.
The gate validates tokens, accepts mirrored events, manages platform keys, tracks deploy/push work, and centralizes admin control.
Prospects see live surfaces, admins see receipts, and client deployments can be sold as infrastructure instead of one-off websites.
What can be sold
Not just a site. A serious operating layer.
This is the angle for client work: anyone can publish a homepage, but most companies still have no controlled intake, no authenticated command deck, no proof trail, no AI-safe routing, and no clean way to hand work from a buyer conversation into delivery.
Founder-led companies
Turn the founder's messy operating reality into a command deck with intake, priorities, proof, and follow-up lanes.
Service businesses
Give sales, delivery, client success, and admin work a shared place to route actions and preserve accountability.
Companies without a site
Launch the public site and the behind-the-scenes operating system together so the business starts with structure.
Existing websites
Drop in a command deck that gives the old site a live business brain, proof router, and authenticated admin surface.
Integration contract
The public shape of the gate.
| Surface | Path | Public meaning | Boundary |
|---|---|---|---|
| Auth introspection | /auth-introspect or /.netlify/functions/auth-introspect | Apps verify bearer tokens through the gate. | Requires server-side token handling. |
| Platform events | /platform/events | Apps mirror proof, monitor, task, and activity receipts. | Requires a server-only mirror secret. |
| Admin events | /admin/platform-events | Operators inspect mirrored history and monitor activity. | Admin protected. |
| App login/session | /auth/app-login, /session/token | Bridges users into downstream apps without sharing owner secrets. | Configuration and approval required. |
| Push/project tracking | SkyeGate Push routes | Deployment work can be tracked as a gate-owned surface. | Provider credentials stay admin controlled. |
Buyer fit
Use this to qualify a company quickly.
A strong fit is a business that needs more than a nice homepage: they need better intake, sales follow-up, internal routing, proof, admin visibility, or a client portal that actually moves work.
Deep map
The full architecture file remains the living source.
What THE_GATE_MAP.md covers
The living map documents the Netlify lane, Cloudflare Worker lane, token introspection, session bridge, OAuth/OIDC/JWKS, platform event mirror, admin event review, push/project tracking, database tables, environment contract, MetrAIyux integration, consumer integration model, security boundaries, usage flows, verification commands, and update rules.
How this connects back to the actual gate
This proof page is the public explanation layer. The live FS27 gate remains the operational layer at https://skyegatefs27-citadeldb.graylondonskyes.workers.dev/. MetrAIyux 0S consumes that gate through bearer introspection and mirrored platform events.
How to use it in a sales conversation
Start with the buyer's operating pain, not with infrastructure. Show the public command deck, show the gate proof surface, then explain that the buyer can receive a branded website plus an authenticated command deck with proof receipts, routing, and admin control.