GURUS AI · LIVE ACTION · BUILD STANDARD
The agent is the interface.
Every page has a job.
This blueprint governs the Gurus Digital Employee site. It records Guru’s established agent-led requirement and turns it into a build and release workflow. Gurus AI’s ongoing collaboration with ChatGPT and OpenAI technology informs the reasoning and development; authority remains explicitly scoped.
The page contract
- Presence: a named agent and mission appear when the visitor arrives.
- Interaction: the agent accepts a useful instruction or directs the next task.
- Work: a control performs a real, bounded operation. Explain, capture, calculate, save or hand off.
- State: show ready, working, paused, completed or blocked only from observed evidence.
- Control: STOP is visible; its limits are explicit. No silent external action.
- Proof: distinguish user input, browser notes, server records, examples and verified outcomes.
- Continuity: preserve the work and give the next agent the relevant handoff.
The page agents
| Workspace | Agent | Responsibility |
|---|---|---|
| /homecoming | Meet-and-Greet Guide | Prepare your first task and connect you with Guru’s learning or business path. |
| / | Scout | Find the first responsibility worth handing over. |
| /business-package | Scope Agent | Turn your business need into a clear scope before pricing. |
| /plans | Service Guide | Show what this service does and where you remain in control. |
| /portal | Deployment Agent | Prepare your approved business information for deployment. |
| /admin | Operations Agent | Help Guru review evidence and choose the next client action. |
| /admin/pricing | Quote Agent | Calculate setup and ongoing service from the actual work. |
| /activate | Connection Guide | Guide the authorized owner through connection setup. |
| /activate/community | Community Guide | Connect the member’s first useful action to their learning path. |
| /media | Learning Guide | Turn the walkthrough into one useful business action. |
| /blueprint | Workflow Auditor | Check that every page leads to action, evidence and a handoff. |
The operating workflow
Observe ↔ Think ↔ Act ↔ Verify ↔ Learn ↔ Remember ↔ Adapt ↔ Act. Agents collaborate through scoped handoffs. Humans monitor, approve authority and correct results.
- Scout identifies the business job from the owner’s words.
- Scope Agent captures the responsibilities, current process, connections, workload, authority and continuing support.
- Quote Agent calculates from assessed costs; no universal setup price.
- Deployment Agent configures the approved scope, tests it and records the owner handoff.
- Service Agent reviews operation, support, corrections and the monthly report.
- Auditor checks Proof of Work before treating an outcome as verified or expanding authority.
The site currently provides guided scope capture, service walkthroughs, an existing work-audit endpoint and authenticated client/owner forms. This role map does not claim that every role is a separate autonomous backend worker. Browser-only scope notes are not yet sent to Gurus. Customer deployment and payment verification require their actual receipts.
The build workflow — before any page is published
- Read AGENTS.md and this blueprint. Inspect the working page and existing interactions.
- Define the page agent, mission, input, action, authority, state, evidence and handoff.
- Implement the useful operation first, then design the agent’s presence and mobile workspace.
- Preserve working components and use the established assets. Bright, readable, mobile-first design; no static brochure as the primary experience.
- Verify the action, STOP/resume, failure state, restoration and handoff. Inspect phone layout.
- Run the page-agent contract check, type check and appropriate integration tests. Build and publish the exact checked source.
- Inspect the live result, save Proof of Work and record any remaining blocker accurately.
Release gate
- A picture, animated status or chat button alone does not pass.
- No fake online status, job execution, revenue, delivery or model connection.
- A static form may support the job, but the page must give context, direction and an accountable next move.
- Every new page must be added to the page-agent registry and covered by the build check.
- Unknown costs stay unknown. Keys never enter scope notes or receipts.