01
It is not a generic chat system
AI mainly acts as the decision entry and capability-recommendation layer. The real goal is to move scripts and workflows into a governed execution chain.
Quick Start
Getting Started
Quick OverviewExecGov is not a single chat page. It is already an execution platform with four practical paths: the free path, local script slots, the formal team edition, and enterprise delivery.
First identify which layer fits you now, then decide which pages deserve your time.
This quick-start page exists to help you determine, through the shortest possible path, which route is currently available for direct experience, expansion, upgrade, or a deeper conversation.
Understand in 10 minutesPublic entryLocal script slotsCLI pathTeam / enterprise
EXECGOV // QUICK STARTGUIDE 02
const publicEntry = ['experience', 'login', 'register']const productRoute = ['docs', 'delivery', 'deployment']const localBridge = ['cli_login', 'register', 'run', 'agent']
START WITH WHAT YOU CAN USE NOW
02
It already has public entry points
You can now use the experience page, login page, signup page, and docs site directly, without detouring through older entry points.
03
It already has a delivery mainline
There are now two practical delivery paths: standard shared-SaaS tenants and enterprise single-tenant delivery. There is no longer only one formal onboarding mode.
04
It already has a CLI bridge
execgov-cli already covers login, registration, listing, execution, and the Agent skeleton entry points.
Path First
First decide which layer you are in right now
| Your current state | Best-fit path | What to read first | What not to rush into |
|---|---|---|---|
| You are touching the platform for the first time | Start with the free path | Experience page, signup page, Getting Started | Do not interpret it as an enterprise project from the first minute |
| You already keep connecting scripts in your personal space | First decide whether local script slots need expansion | Billing & Membership, local script-slot notes | Do not treat lightweight personal expansion as a formal team subscription |
| You are preparing for multi-user collaboration | Start with the formal tenant entry for the team edition | Billing & Membership, Customer Flow / Delivery | Do not assume that private deployment is automatically the first step |
| You involve intranet constraints, stronger isolation, or formal project acceptance | Go straight into enterprise-delivery discussion | Deployment, Customer Flow / Delivery, Contact | Do not continue using the personal-entry or standard-membership narrative |
Current Entry
How to understand the current public entry points
| Entry | Current status | Best for | Notes |
|---|---|---|---|
/experience | The current formal public experience page | People trying it for the first time | This is a real entry point, not a screenshot placeholder. The left side currently shows Python task_brief_demo.py, the right side shows Shell clean_log_demo.sh, and the experience scripts come from the formal directory exec-gov-ai-skill-platform-script/tenant_1000/experience/. |
/login | The current formal login page | People who already have an account | Used to enter the personal free edition or later a formal tenant space. |
/register | The current formal signup page | People who do not have an account yet | After registration succeeds, the current flow enters a dedicated result page before returning to login and the personal mainline. |
/register/result | The current formal result page | People who just completed signup | It explicitly handles the next step after signup instead of relying only on a success toast. |
| Product docs | Already structured as a system | Product, technical, and presales roles | Explains what the platform is, how it is delivered, how it is deployed, and how it evolves. |
| CLI docs | Already structured as a system | Developers and local-bridge scenarios | Explains the current command boundary: what is implemented and what is not. |
| Contact page | The current formal entry | People who want to continue | Used to determine whether to stay on the free path, expand local script slots, move into the team edition, or go into enterprise delivery. It is no longer a generic contact page. |
Try First
Experience path
- Start with the public experience path and feel the closed loop of AI recommendation and execution.
- Then read Product Overview to decide whether this is the type of platform you actually want.
- If you need long-term use, register and log in next.
- Then decide whether you need the CLI path or the team / enterprise path.
Local Script
Local script onboarding path
- First confirm which commands
execgov-clialready supports. - Then prepare your script directory and README.
- Understand the current boundary of
register / list / run / agent. - If the work belongs to a real project, move on to hybrid-execution and delivery boundaries.
Delivery
Team / customer delivery path
- Start with Customer Flow / Delivery to understand real usage and the hot-update path.
- Then read Deployment to decide whether you need shared SaaS, a single tenant, platform governance, or hybrid execution.
- Confirm the edition and delivery model that actually fits you.
- Finally use the Contact page to determine whether to keep moving through the standard team edition or go straight into enterprise delivery.
Before You Start
Know these things before you begin
- The public experience page is meant to demonstrate the execution chain first. It does not take real business writes.
- The current demo on the experience page comes from
exec-gov-ai-skill-platform-script/tenant_1000/experience/and is mapped through the manifest for hot swapping. - After signup, you enter the personal intelligent execution console and can start onboarding your first script.
- Web upload-based registration already supports
.py / .sh / .bash. execgov-cliis also adding Shell support, but the primary examples and default guidance still lean toward Python for now.- If you are only continuing as an individual user and have not entered multi-user collaboration yet, start with local script-slot expansion instead of jumping to the enterprise path.
- If you only need standard capability and lighter collaboration, evaluate the shared-SaaS tenant path first.
execgov-cliis already usable and its local-integration capability will continue to get stronger.- If you already know this is a formal team workflow or an enterprise project, moving directly into the team / enterprise path is usually more efficient.
Current Stage
What usage modes are covered at the current stage
- The enterprise
1.0delivery mainline has been established. - The personal free entry has been established.
- The standard shared-SaaS tenant frontend has been established and is still being tightened.
- The minimal CLI bridge is already in place.
- Standard team-collaboration capability and richer packaging will continue to expand.
Next Read
Common entry points after the first-pass decision
Continue by goal: product overview, customer delivery, CLI docs, or FAQ, without bouncing between all pages.