Centronium Intelligence OS

SkyMind Owner's Manual

This guide explains how to create an application from scratch, import an existing codebase, verify persistent files, preview and edit the project, ask SkyMind to continue building, run quality checks, prepare actions, and package releases.

Easy ModeDescribe the outcome in plain language.

Real filesEvery saved change appears in the persistent file tree.

Safe actionsWrites pause for approval and leave receipts.

Product map

One SkyMind, clear modules

SkyMind 2.0 now uses one main product entry point at /skymind/. The capabilities developed in earlier Stable, Alpha, and Beta surfaces are presented as named parts of the same workspace.

Module	Purpose
Chat	Conversation, live search, research, code, attachments, Network Agent, and first-party answers.
Projects	Persistent files, Project Copilot, previews, tests, diffs, imports, baselines, and releases.
Frontier	Task profiling, intelligence modes, verification contracts, and repair-first reasoning.
Network	CentroSky capacity, provider health, incidents, notifications, and first-party certification.
Actions & Workflows	Approval-gated operations, receipts, and recurring multi-step work.
Memory	Personal, project, network, conversation, and experience memory controls.
Intelligence Lab	Measured model scorecards, evaluation suites, and routing telemetry.

Compatibility paths/skymind-alpha/ and /skymind-beta/ are retained only as transition entry points. They redirect into the matching SkyMind 2.0 modules instead of acting as separate products.

Project Copilot

Build a new application

Open Build an AppChoose New app.

Name and describe the productExplain what the app should do, who uses it, and the most important features.

Select the type and designChoose website, web app, AI assistant, dashboard, store, news site, game, or API.

Choose featuresAccounts, admin, mobile navigation, live data, profiles, notifications, dark mode, PWA, and SEO can be included.

Build and show my filesSkyMind creates the protected project, saves the starter files, shows a file receipt, and opens the workspace.

Example brief

Build a modern task-management web app called CentroTasks. It needs user accounts, projects, task statuses, due dates, a dashboard, mobile support, dark mode, and an admin area.

What should happenYou should see an active-project bar, a receipt listing real files, a live preview, a file tree, and an editor. A plain text answer without a project or files is not a completed build.

Existing code

Import a ZIP, folder, or files

Choose Import projectGive the workspace a name and description.

Select the sourceUpload a ZIP, individual files, or a complete folder.

Import and inspectThe protected ZIP importer rejects path traversal and symbolic links, enforces file and expansion limits, and restores overwritten files if an import fails.

Verify the resultOpen the file tree, check the preview entry, and ask SkyMind to explain the architecture.

Protected filesFiles such as .env, private keys, and credentials remain in the protected workspace and release ZIP, but their contents are never shown in the browser or sent to the model.

Persistent workspace

Work with real project files

The active-project bar confirms which project SkyMind should use. The Builder workspace has five connected views:

Conversation: tell SkyMind what you want improved; it discovers relevant files and prepares reviewable changes.
Preview: a sandboxed rendering of the selected HTML entry file.
Files: a readable inventory of the persistent project source.
Editor: direct editing for text and code files up to the editor limit.
Changes: plans, file diffs, validation receipts, and undo controls.

How to know a change was saved

A completed write shows a green project receipt with the exact created or modified file paths. Suggestions, plans, and code examples must not be described as saved changes.

Saved to persistent project Files modified - assets/css/app.css - assets/js/app.js - dashboard.html

Project Conversation

Open the project and tell SkyMind what to improve

Project Conversation is the default project experience. You do not need to choose Edit, Debug, Plan, or a model before starting. Open a saved project and describe the outcome in plain language.

Describe the improvementExample: “Modernize the admin area but preserve authentication and current API behavior.”

SkyMind discovers relevant filesThe project file tree and instructions are searched automatically. @file remains available when you want precision.

Review the proposalSkyMind explains the recommended update, lists exact files, shows before/after excerpts, runs deterministic checks, and uses Frontier verification when appropriate.

Approve, revise, or cancelApprove & apply writes the project. Ask for changes replaces the pending proposal with a revised review-first proposal. Cancel writes nothing.

Continue naturallyAfter save, checks and a receipt are shown, Preview refreshes, and Undo remains available.

Natural requests

Make the admin area more professional but keep authentication exactly as it works now. Find why the mobile menu breaks and fix it. What are the five biggest improvements you recommend for this project? @config.php explain this file and tell me whether it should change.

Normal write policyProject Conversation defaults to review before changes. Mode, intelligence, and direct editing still exist under Advanced controls for users who explicitly want them.

Status is literalProposal only means nothing changed. Waiting for approval means exact changes are ready. Saved to project appears only after the trusted server writes files and runs checks.

Conversation bridge

Add normal-chat files to a project

Uploaded attachments, code blocks, complete SkyMind answers, multi-file attachment packages, and generated artifact packages include Add to Project. Imports are checked before writing, grouped into auditable batches, and can be undone while the imported version remains unchanged.

Choose Add to ProjectSelect the destination project.

Choose the pathPlace the file in a folder such as admin/, assets/js/, docs/, or the Project Inbox.

Handle collisionsCompare first, replace explicitly, or save under a new name.

Add or ApplyAdd copies the file only. Apply also asks Project Copilot to integrate it, but related edits remain review-first.

Open Project ConversationThe receipt opens the exact persistent project and imported file. Added from Chat preserves the source, original goal, checks, destination, and undo state outside the source code.

Safe defaultUse Project Inbox when you do not yet know where a generated file belongs. Nothing is wired into the live application until placement or integration is reviewed.

Quality

Preview and test the application

The preview runs inside a sandbox. Local CSS, JavaScript, and images are inlined. Server code, external requests, service workers, and real form submissions remain disabled.

Use Desktop, Tablet, and Mobile buttons to inspect layouts.
Refresh the preview after saving files.
Run project checks before packaging a release.
Warnings may be acceptable; failed checks should be fixed before staging.

The quality suite checks project files, size, secrets, HTML IDs, accessibility basics, local assets, JSON, PHP, CSS, JavaScript, inline handlers, and the preview entry.

Action Network

Actions, approvals, receipts, and undo

Risk	Behavior
Read-only	Can run immediately.
Reversible	Waits for click approval and may offer undo.
Consequential	Requires typed confirmation.
Blocked / approval-gated	Funds, purchases, outbound messages, public posts, ownership changes, and production deployment.

Every action records the application, action type, payload, risk, status, result, time, and undo availability. Secret values are redacted.

Automation

Build safe workflows

Easy Mode workflows use the pattern:

When this happens → run this read-only action → then run another action → pause before any write

Scheduled and event-driven workflows can execute read-only steps automatically. The first reversible or consequential step creates an approval and pauses the workflow. The master lifecycle cron processes due workflows; no separate module-specific cron is needed.

Shipping

Baselines, checks, and staging releases

Save a baselineRecords hashes for the current project files.

Make changesAdded, modified, and deleted paths appear in the change ledger.

Run checksReview the score, warnings, and failures.

Build stagingA typed BUILD confirmation packages source, release metadata, deployment instructions, tests, and checksum.

SkyMind does not silently deploy to production.

Trust

Privacy, permissions, and first-party access

Public services can be used without private permission. Wallet, mining, messages, and private activity each require their own enabled permission. Access History separates:

Actual access: a service was contacted and returned data.
Needs attention: a route was contacted but failed authentication, latency, or schema checks.
Privacy boundaries: private data was not accessed because permission remained off.

First-party certification tracks schema, latency, recent failures, last success, and quarantine status.

Support

Troubleshooting

No files appear after building

Refresh SkyMind, open Projects → Continue project, and select the project. If its file count is zero, the starter creation failed and should show a request error.

SkyMind gives code but does not save it

Open the project Conversation and describe the improvement in normal language. Proposal only means nothing changed. Waiting for approval means a validated file plan is ready. Saved to project includes exact files, checks, and undo.

A conversation file belongs in a project

Use Add to Project beneath the attachment, code block, or answer. Choose a project and destination. Use Add to Project Inbox when placement is uncertain.

Preview is blank

Verify the project entry file, check for missing local assets, and run project checks. PHP applications can only show their static HTML entry inside the safe preview.

Wrong project or stale context is used

Open Current Context. Choose a project and select Switch project to change the project/file boundary without discarding the current conversation. Choose New chat in project to start clean conversation history while keeping that project available. Choose Fresh chat · no project to clear both conversation history and project context for a genuinely fresh request. The Current Context summary must show the intended project before any project write.

ZIP import fails

Check file size, archive expansion, entry count, symbolic links, and unusual paths. Failed imports roll back instead of leaving a partial overwrite.

First-party route fails

Open Certification or Access History to find the schema, HTTP status, request ID, latency, and fallback state.

Best diagnostic sentence“Show the active project, list the persistent files you inspected, state which files you actually saved, run checks, and give me the request ID for any failed tool.”

Frontier Intelligence Core

SkyMind 2.0 includes a measurable Frontier Intelligence layer inside the unified workspace. Frontier Router V2 profiles requests by task, complexity, freshness, risk, project context, tools, and verification needs. The Frontier Intelligence view exposes real model telemetry, evaluation snapshots, five memory layers, and tool verification contracts.

Project Copilot intelligence

Project Copilot can run in Auto, SkyMind Pro, or SkyMind Frontier intelligence modes. Frontier project edits receive deterministic pre-write checks plus an independent model review. If the reviewer detects material issues, SkyMind attempts a repair and returns the repaired proposal for human review rather than silently saving it.

Evaluation policy

Model scorecards use actual CentroSky run telemetry. Evaluation suites without curated expected outputs remain unscored rather than receiving invented benchmark numbers.