gonuEngineering Brain: your software and its history
Connect repository structure, engineering decisions, incidents and selected documents. Inspect evidence before planning, changing or recovering work.
WHEN IT HELPS
Put it to work.
Understand why a system exists, what a proposed change may touch, and what a new teammate needs to know. Keep deliberately shared decisions after an employee leaves.
Before you begin
- Backend migration 034; an authorized project and workspace.
- Repository scanning and web execution require files in an existing managed server project. Local folders are never silently uploaded.
- Execution requires a configured model and the existing authorized tool runtime. Rehearsals require the separate offline Docker executor.
EXPLORE EACH WORKFLOW
15 features. Individual demo screens.
Read the use case, click through the sample workflow, and check what is implemented or still pending.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Open Engineering → Engineering Brain, select your workspace/project, and scan. Counts, syntax relationships, Git history, configuration discovery and review candidates come from the actual accessible files. Scans reuse the incremental index.
Add a decision, service, incident, ticket, ownership record or measurement; link known files and selected sources. Confirm sharing with the project. Edits retain revisions. Ask the Company retrieves evidence from permitted projects, with dates and references.
Future Scenarios traces import candidates, related tests and linked decisions. Optional capacity/cost arithmetic uses the inputs you supply. Excluding a decision explores assumptions, not a factual alternate history. Use Change Rehearsal for actual baseline/alternative command results.
In CTO & System Builder, state a goal, acceptance criteria, existing check commands and a usage cap. Prepare a shared task, generate a real plan, then approve each consequential step. Build mode uses the existing metered build/test/review pipeline. Missing integrations and previews remain explicit.
Enable a metadata monitor and optional incident repair drafts. A supplied fresh metric can trigger a threshold incident. Replay real phases, inspect evidence, prepare a file rollback or extract a reviewed private skill from a verified task. Export onboarding and project knowledge when needed.
Illustrative scan / no benchmark
THE USEFUL RESULT
What you should leave with.
A source-grounded engineering workspace linked to existing tasks, budgets, approvals, evidence and skills. Shared decisions are also retrieved into relevant project chat across models and clients.
Know the boundaries.
- Import relationships and test-gap candidates are heuristics. No fabricated services, expertise ratings, capacity forecasts, ROI or 60-second guarantee.
- The current monitor checks repository metadata and supplied measurements. Live CVE feeds, repeated flaky-test runs and production telemetry are not automatic checks.
- Production canaries, database/cloud/ticket rollback and external system provisioning need reviewed deployment-specific integrations. File restore does not undo these effects.
- Ask the Company retrieves authorized sources and links; it does not prove causal relationships or silently query Slack, email, cloud systems or personal memory.
- Historical repository snapshots are joined to sources currently authorized for the viewer. Full historical source reconstructions are not claimed.
IF SOMETHING DOESN’T WORK
A scan or task is unavailable, or a result is incomplete.
Check project access and whether the repository is local or managed. Scan managed files first. Read task evidence and approval state; never rerun uncertain work automatically. Configure the existing executor/model, or use local Worker/CLI/VS Code tools for a device-only repository.
Contact support