Is this just a normal chat system
No. It is a platform that lets AI call and execute real capabilities inside rules. The most mature execution asset today is the Python script, and web-side upload registration already supports both Python and Shell.
FAQ
FAQ
Key QuestionsMost public questions still cluster around positioning, isolation, hot updates, the CLI bridge, and the current stage.
This page answers the questions that show up most often in public conversations.
This page is for the questions that come up most often during a first conversation, a first product experience, or a first delivery discussion. Its job is not to retell the concept, but to explain the positioning, boundaries, isolation model, hot-update path, CLI / Agent status, local execution model, and current stage in one place.
PositioningIsolationHot UpdateCLI / Agent
EXECGOV // FAQGUIDE 03
positioning / boundary / current_stagetenant_isolation / hot_update / public_safe_docscli_bridge / local_execution / team_delivery
CLEAR BOUNDARIES SAVE EVERYONE TIME
Positioning
Positioning
Who is it for
It fits people who already have scripts, automation work, data-processing needs, or a need to turn those capabilities into one unified entry, one delivery path, and one governance model.
Is the free edition just a trimmed enterprise backend
No. The free edition is for individual explorers. It is meant to let them quickly experience capability onboarding, AI scheduling, and execution feedback before moving into team or enterprise collaboration.
Are the free path and enterprise path two completely separate systems
No. They share the same execution and security foundation. What changes is the scale of use, the depth of collaboration, and the delivery model.
Is there only one formal path right now
No. The public story is already split into four layers: the free path, local script-slot expansion, the formal standard team edition, and enterprise / private delivery.
Safety
Security, isolation, and permission boundaries
Can AI execute beyond its authority
The platform is explicitly designed so AI works inside rules. Recommendation scope, execution boundaries, manual confirmation, and audit trails are built-in governance layers, not optional decoration.
Can one customer see another customer's capabilities
No. Whether the model is shared SaaS or enterprise single-tenant delivery, customers only see the capabilities they are authorized to use inside their own tenant.
How is customer isolation enforced
The platform isolates capabilities, data, and permissions by customer boundary by default so different customers remain invisible to one another and do not interfere with each other.
Can AI recommend capabilities from another tenant
No. The recommendation scope is constrained by both tenant boundary and permission boundary. It is not a model that can recommend whatever it happens to think of.
Delivery
Delivery and hot updates
Do we have to start with private deployment
No. Standard team collaboration can usually start through the shared-SaaS formal tenant entry. Private deployment or enterprise delivery only becomes the better path when stronger isolation, intranet access, local bridging, or formal project acceptance is actually required.
Does a hot update require redeploying the whole platform
No. Once the customer script passes review, sync, registration, and authorization, it can take effect inside the current tenant without redeploying the whole platform.
Can a customer upload a script and put it into formal production immediately
Not in the default 1.0 path. The platform still keeps review, registration, authorization, and permission-verification steps in place. It does not support bypassing the platform and going live directly.
Can a customer upload any frontend page and publish it directly
No. Existing formal pages, external links, and iframe entries can be attached to menus, but adding a new formal frontend page still requires development, packaging, and deployment. Shared SaaS does not let tenants upload arbitrary Vue / JS bundles as formal product pages.
Will a hot update affect other customers
No. After a script update lands, it only takes effect inside the owning tenant. Other tenants do not automatically gain visibility or execution rights.
Does every project include file upload and result download by default
Not necessarily. If the project needs to handle input files and result artifacts, the platform can provide file upload, batch status, and result-download flows, but whether they are opened still depends on project scope.
After a file is uploaded, how does the script know which file to process
The script does not guess. The upload button in the execution quick bar binds the current upload as one uploadBatchId, and during confirmation the backend passes a snapshot of that batch into the script. Python and Shell scripts can read EXECGOV_UPLOAD_BATCH_NO, EXECGOV_UPLOAD_INPUT_FILES_JSON, EXECGOV_UPLOAD_FILE_SERVICE_JSON, and EXECGOV_SKILL_INPUT_PAYLOAD_JSON, so they operate on the bound batch rather than some guessed “latest file” in a historical directory.
What documentation does a customer usually receive after formal delivery
At minimum, customers should receive the access entry, the account method, customer-usage instructions, and customer-side script hot-update instructions. If the project also includes announcements, customer notices, or result-download entries, those should be explained together.
CLI & Local
CLI, local scripts, and the Agent path
Is the CLI still only conceptual
No. execgov-cli already supports login, register, list, run, agent describe, and agent start. It is already usable for local onboarding, debugging, and early validation.
Is the local Agent already a finished commercial feature
Not yet. The local Agent direction is still being strengthened, and for now it should be understood as a local bridge and execution skeleton rather than a finished product line.
Can local scripts and intranet resources connect to the platform
Yes, but usually not by exposing local paths directly to the browser. The normal approach is to use the CLI / Agent path as the local execution bridge.
Are all script types fully supported for remote onboarding already
Web-side upload registration already supports Python and Shell text scripts. CLI-side remote registration still mainly centers on Python today, with more types to follow later.
Stage
Current stage and upgrade path
What already exists today
The enterprise 1.0 delivery mainline, the personal free entry, the minimal CLI bridge, and the external docs site are already usable. They can support public explanation, free-path experience, and part of the real scenario flow.
Is the standardized small-team edition already fully open
Not yet in its final form, but the shared-SaaS frontend already exists and the monthly / yearly upgrade path is already present. What remains to be tightened is branding, initialization, and finer menu boundaries.
What should the experience page help me judge
It should help you feel the execution chain, understand the platform position, and decide whether you belong on the free path, local script-slot expansion, the standard team edition, or enterprise consultation. The current experience page shows Python task_brief_demo.py on the left and Shell clean_log_demo.sh on the right, sourced from exec-gov-ai-skill-platform-script/tenant_1000/experience/.
Where do I go after signup succeeds
The current flow enters a dedicated result page first, then returns to login and the personal mainline. It no longer depends only on a toast message.
Is exec-gov-shell the formal customer entry
No. It mainly exists for multi-entry aggregation, joint debugging, and sync. Formal customer entry still means the personal free frontend, the shared-SaaS tenant frontend, or the enterprise-delivery frontend.
Next Read
Common next pages after FAQ
Continue by goal: Product Overview, Customer Flow / Delivery, the CLI Guide, or direct lead routing.