Ask Gene — GeneWorks

You should not have to know which specialist to ask.

Gene is the orchestrator and the only entity you interact with directly. It classifies intent, routes to the right specialist, enforces the two sign-off gates, synthesises the outputs, and holds authoritative task state. Active locks prevent concurrent conflicting changes on the same resource.

You ask the question you actually have. The routing is not your problem.

3kinds of request

What people actually ask

Ask Gene covers the work that does not justify a full delivery cycle — the questions, the one-off tasks, and the investigations that otherwise sit in someone's queue for a week.

Investigate — what stands on sys_user, what happens if priority becomes mandatory, why a rule did not fire.
Produce — a report of incidents assigned to the network team, a CMDB data quality check on the server class, a technical design document.
Plan — sketch a returns app, or work out what it would take to add a second authoritative source to the CMDB.

You say	Gene routes to
Incident, Problem, Change, SLA, Catalog, Knowledge, Request	ITSM specialists
Discovery, CMDB, CI, Service Mapping, Event, Alert	ITOM specialists
ACL, Role, License, User, Audit, Performance, Admin	Platform & SecOps
REST, API, webhook, IntegrationHub, Jira, Slack, SCCM	Integration specialists

4products it sits inside

In contextopened from a finding

findingF1 stale CIs · 60 days

youwhy does this matter?

Generouting impact, not just hygiene

nextpropose change

It already knows which finding you are looking at. You do not restate the context.

Everywhere, with context

Ask Gene is not a separate destination. It sits inside every product and every application workspace, carrying the context of wherever you opened it.

In Design — interrogate the instance graph or a single application without leaving the map.
In Build — explain a task, adjust a plan, or ask why the planner ordered something the way it did.
In Verify — ask what a failing assertion means and what self-healing attempted.
In Optimize — every finding carries an Ask Gene action that explains the score and the remedy.

~65%steady state, month 6+

Memory, not a fresh session

Gene works against the workspace, so your idioms, ACL patterns, integration map, and prior decisions accumulate rather than resetting between conversations. Proposals converge on how your team actually builds.

Analysis data, run history, and lessons are stored per workspace. They are never pooled across tenants or used as model context for another customer.

Effort reductionas workspace memory matures

cold start · week 1–425–35%

context maturing · month 2–340–50%

compounding · month 4–655–60%

steady state · month 6+~65%

Week one is fine. Month six is the point.

You should not have to know which specialist to ask.

What people actually ask

Everywhere, with context

Memory, not a fresh session

Asking is not the same as doing.

Put a real question to it.