Early stage · v1.16.1
A semiconductor IP company, as software.
IP Nirmaan is an AI-native semiconductor IP company modeled as software: you give it a requirement, and a machine-readable organization plans, routes, reviews, and gates the work, with evidence behind every claim.
$ nirmaan plan "Create a 4-port AXI-to-NoC bridge." PROJECT: Create a 4-port AXI-to-NoC bridge Intent: new_ip Features: axi, cdc, multi_port, noc, registers Assumption: Clocking was not stated, so CDC/RDC work is planned conservatively. PROGRAM MANAGER Senior Technical Program Manager ├── Architecture (lead: Chief Architect) │ ├── Interface specification: AXI interface owner: Senior AXI Interface Architect │ ├── Microarchitecture owner: Staff NoC Microarchitect │ └── GATE Architecture approval owner: Chief Architect (human approval) ├── RTL (lead: Director, RTL Engineering) │ ├── RTL implementation: AXI slave interface owner: Senior Interface Design Engineer │ └── RTL implementation: Arbitration owner: Senior Interconnect Design Engineer ├── Verification (lead: VP, Verification) │ ├── Verification plan owner: Senior Verification Planning Engineer │ └── Coverage closure owner: Senior Functional Coverage Engineer └── Signoff └── GATE Verification signoff owner: VP, Verification (human approval)
nirmaan plan, trimmed.The idea
Engineering work, run by an organization you can read.
-
An organization, not a chatbot.
Divisions, teams, and roles from intern to CEO, each with skills, authority, and an escalation path.
-
Planned is not done.
Work moves through planned, executed, verified, and approved, and nothing skips a step.
-
Evidence or it did not happen.
A tool run, a review, or a named person's sign-off backs every claim. An AI cannot mark its own work approved.
- planned A plan with an owner
- executed A recorded tool run
- verified An independent review
- approved A named human's sign-off
Refused An AI worker asking to approve its own work is turned away: nobody approves their own work.
How it works
From one sentence to routed, gated work.
Follow one requirement through the organization. Scroll to move it along.
-
Requirement
A plain-language request comes in. Nothing else is needed to start.
-
Analyze
Intent, features, and parameters are extracted. Anything left unstated becomes a written assumption, not a silent guess.
-
Route to roles
Each task goes to the role whose skills, capabilities, and authority fit it. Routing reads the organization as data.
-
Review and gate
Work is executed, then verified by an independent reviewer. Gates such as architecture approval wait for a named human.
-
Deliverable
The work product arrives with its trail: who did what, from which inputs, backed by which evidence.
Requirement Create a 4-port AXI-to-NoC bridge.
- axi
- noc
- multi_port
- cdc
- registers
Assumption Clocking was not stated, so CDC work is planned conservatively.
- Interface specification: AXI Senior AXI Interface Architect verified
- Microarchitecture Staff NoC Microarchitect verified
- GATE Architecture approval Chief Architect (human) approved
- RTL: AXI slave interface Senior Interface Design Engineer verified
- RTL: Arbitration Senior Interconnect Design Engineer verified
- Verification plan Senior Verification Planning Engineer verified
- GATE Verification signoff VP, Verification (human) approved
What the organization looks like
A whole company, defined as data.
- 207organizational units
- 685roles, from intern to CEO
- 140engineering skills
- 7engineering workflows
- 12constitution principles
- 42verification knowledge packs
- 880automated tests
- Product
- Architecture
- Design Engineering
- Verification
- Silicon Implementation
- Software
- Security
- Infrastructure
- Documentation
- Quality
The company constitution
Twelve principles the engine enforces.
- P1
Traceability
Every task traces to the requirement it serves.
- P2
Evidence for decisions
Important engineering decisions require evidence.
- P3
Explicit uncertainty
Agents must explicitly represent uncertainty.
- P4
No fabricated work
Agents must not fabricate completed work.
- P5
No fabricated tool runs
No claim that a tool ran unless it did.
- P6
Independent review
Critical work is reviewed. Nobody approves their own work.
- P7
Conflicts escalate
Conflicting outputs are escalated before approval.
- P8
Provenance
Every change records who, what, and from which inputs.
- P9
Evidence for signoff
Signoff requires evidence.
- P10
No hidden state changes
Every change goes through the engine and the audit trail.
- P11
Auditability
The audit trail is append-only and hash-chained.
- P12
Human approval at gates
Gates can require a human to approve.
Built on VeriTriage
The verification engine inside.
VeriTriage is the verification-intelligence engine inside IP Nirmaan. It turns simulation logs, coverage, and waveforms into an evidence graph and a ranked, evidence-backed root cause.
When IP Nirmaan triages a regression, VeriTriage does the investigation, and its results become evidence in the task.
Status and roadmap
Early, open, and honest about it.
Working today
The organization model, planning, routing, reviews, gates, the audit trail, and real VeriTriage investigations.
Next
AI workers in verification roles, then connections to open-source design tools, then design and RTL agents.
Not yet
No chip or IP block has been designed or delivered by the system.