Four editions. One cumulative capability ladder.

Every edition lives on the same NCT core and the same Canonical Engineering Reality. Entry is deliberately complete and competitively positioned; capabilities can move downward across editions as the market evolves without rebuilding the product. L5 remains an Enterprise depth.

EDITIONS

Editions

Entry Bring a project under control. — Human development · optional single AI · foundational engineering control
Standard Bring AI collaboration under control. — Single / dual AI · governed collaboration · independent verification patterns
Professional Bring complex engineering relationships under control. — Architecture · impact · contracts · RCA · debt · advanced validation
Enterprise Bring long-term engineering evolution under control. — Organization governance · private AI · provider policy · long-term engineering intelligence

CAPABILITY DEPTH · ONE CORE

Four editions. One cumulative capability ladder.

L1 Observe & Ground Project reality, files/code/search, Git/diff, health and deterministic facts.
L2 Control & Continue Human development, requirements/tasks, changes, build/test, evidence, engineering memory, context continuity, snapshot/recovery and optional single AI.
L3 Deep Engineering Prove the task: requirement, implementation, tests, evidence, failure paths and architecture integrity.
L4 Cross-Domain Composition Architecture, impact, contracts, boundaries, RCA, debt, advanced validation and relationships across canonical engineering domains.
L5 Engineering Intelligence Cross-episode, temporal and organizational intelligence derived from trusted engineering relationships and long-term outcomes.

CAPABILITY DEPTH · ONE CORE

Four editions. One cumulative capability ladder.

Entry — Includes L1–L2

Individuals and lightweight engineering

AI collaboration: Human / optional single AI

Workspace: W1 primary · Human or Single-AI development

Cumulative depth: Foundation

Foundation capabilities:

Project scan & understanding
Files · Code · Search
Git · Diff · Terminal
Build · Test
Basic Architecture
Requirement / Task
ChangeSet
Basic Evidence
Context Continuity
Snapshot / Recovery
Observer / Development
Basic Health / Debt
Engineering Memory
Canonical Project Reality
W1 Development Workspace

Standard — Includes L1–L3

Governed AI collaboration

AI collaboration: Single / Dual AI

Workspace: W1 + W2 collaboration / validation patterns

Cumulative depth: Everything in Entry + L3 collaboration & task proof

Adds at this level:

Governed Single / Dual AI
Work mode & role assignment
Builder + independent verifier
Controlled parallel patterns
Blind independent analysis patterns
Clean AI handoff foundation
Task-scoped context
Independent verification
Evidence-backed task proof
Human authority remains final
W2 Oversight / Validation Workspace

Professional — Includes L1–L4

Complex software engineering

AI collaboration: Advanced governed orchestration

Workspace: W1 + W2 + W3 advanced engineering use

Cumulative depth: Everything in Standard + L4 cross-domain governance

Adds at this level:

Architecture governance
Impact analysis
Contract & boundary governance
Deep RCA
Technical Debt governance
Advanced ChangeSet
Advanced validation
Cross-domain engineering relationships
Native composition
Engineering Relation Fabric views
Advanced context intelligence
Advanced AI orchestration
W3 Architecture / Governance Workspace

Enterprise — Includes L1–L5

Long-term & organizational governance

AI collaboration: Adaptive multi-AI + governed private resources

Workspace: Full W1–W3 organizational use + L5 intelligence

Cumulative depth: Everything in Professional + full L5 long-term intelligence

Adds at this level:

L5 composite intelligence
Cross-Episode intelligence
Organizational governance
Adaptive Multi-AI analysis
Provider policy
Custom / Self-Owned AI governance
Long-term Engineering Reality
Team / scope / device governance
Retention / audit / compliance direction
Sovereign intelligence direction
Higher-depth entitlement as proven

Capability × Editions (cumulative)
Capability	Entry	Standard	Professional	Enterprise
Project scan & understanding	yes	yes	yes	yes
Files · Code · Search	yes	yes	yes	yes
Git · Diff · Terminal	yes	yes	yes	yes
Build · Test	yes	yes	yes	yes
Basic Architecture	yes	yes	yes	yes
Requirement / Task	yes	yes	yes	yes
ChangeSet	yes	yes	yes	yes
Basic Evidence	yes	yes	yes	yes
Context Continuity	yes	yes	yes	yes
Snapshot / Recovery	yes	yes	yes	yes
Observer / Development	yes	yes	yes	yes
Basic Health / Debt	yes	yes	yes	yes
Engineering Memory	yes	yes	yes	yes
Canonical Project Reality	yes	yes	yes	yes
W1 Development Workspace	yes	yes	yes	yes
Governed Single / Dual AI	later	yes	yes	yes
Work mode & role assignment	later	yes	yes	yes
Builder + independent verifier	later	yes	yes	yes
Controlled parallel patterns	later	yes	yes	yes
Blind independent analysis patterns	later	yes	yes	yes
Clean AI handoff foundation	later	yes	yes	yes
Task-scoped context	later	yes	yes	yes
Independent verification	later	yes	yes	yes
Evidence-backed task proof	later	yes	yes	yes
Human authority remains final	later	yes	yes	yes
W2 Oversight / Validation Workspace	later	yes	yes	yes
Architecture governance	later	later	yes	yes
Impact analysis	later	later	yes	yes
Contract & boundary governance	later	later	yes	yes
Deep RCA	later	later	yes	yes
Technical Debt governance	later	later	yes	yes
Advanced ChangeSet	later	later	yes	yes
Advanced validation	later	later	yes	yes
Cross-domain engineering relationships	later	later	yes	yes
Native composition	later	later	yes	yes
Engineering Relation Fabric views	later	later	yes	yes
Advanced context intelligence	later	later	yes	yes
Advanced AI orchestration	later	later	yes	yes
W3 Architecture / Governance Workspace	later	later	yes	yes
L5 composite intelligence	later	later	later	yes
Cross-Episode intelligence	later	later	later	yes
Organizational governance	later	later	later	yes
Adaptive Multi-AI analysis	later	later	later	yes
Provider policy	later	later	later	yes
Custom / Self-Owned AI governance	later	later	later	yes
Long-term Engineering Reality	later	later	later	yes
Team / scope / device governance	later	later	later	yes
Retention / audit / compliance direction	later	later	later	yes
Sovereign intelligence direction	later	later	later	yes
Higher-depth entitlement as proven	later	later	later	yes

FULL ENTRY TRIAL

14-day full trial

Full Entry · real project · bring your own AI account · no token resale

COMMERCIAL MODEL

Low barrier to enter. High ceiling to govern.

NCT is not sold as AI tokens. Customers bring the AI resources they choose; NCT commercializes its own engineering governance, continuity and capability depth.

Entry is a real product — Full Entry functionality, not a crippled trial shell. It is intentionally priced to compete with workflows that often require a mainstream tool plus third-party support.
Packaging can move with the market — The same core allows selected capabilities to move into lower editions through entitlement changes rather than redevelopment.
L5 is Enterprise-only — L5 engineering intelligence is reserved for Enterprise customers and is not represented as a lower-edition entitlement.

L5 ENTERPRISE · SPECIALIZED TOOLING

L5 Super Toolkit is purchased by governance need — not as one giant bundle.

Eligibility requires Enterprise L5 and an annual subscription. Specialized L5 tools are priced independently according to the customer’s business need and governance direction; the entire toolkit is not sold as one package.

SUPER PACK L5 Super Toolkit Enterprise L5 annual customers only. Sold separately — single capabilities or combinations, priced individually by how broadly each one applies.

W1–W3 · FIRST-CLASS WORKSPACES

One product. Three places to work — based on what you are actually responsible for.

W1–W3 are not job titles and they are not L-levels. They are first-class workspaces that let the same NCT core fit an individual developer, a team lead, a principal engineer, an engineering director, a CTO/CIO, or a Chief Architect without forcing everyone into the same interface.

W1 Development Workspace Build safely The daily engineering home: Files, Code, AI Development, Git/Diff, Test, Terminal, Engineering Memory, current task, current context and high-frequency execution. Individual Developer · Senior Developer · Principal Engineer · hands-on leads · Files / Code · AI Development · Git / Diff · Build / Test · Terminal · Current Task · Engineering Memory
W2 Development Oversight · Validation · Management See independently A real development oversight surface for validation, quality and team execution — Observatory, Evidence, Tests, Gap, Performance, Health, Calibration, Development Quality, Team Development, Execution Status and Resources. Tech Lead · Engineering Manager · Engineering Director · verification / quality leadership · Observatory · Evidence · Tests · Gap · Performance · Health · Team Development · Execution Status
W3 Architecture · Governance · Higher-Order Intelligence Expand intelligence without expanding loss of control System-level architecture, governance, authority, engineering relationships, history/time, architecture evolution, cross-team reality and higher-order engineering intelligence. Enterprise Architect · Principal Engineer · CTO · CIO · Chief Architect · Architecture · Governance & Authority · Relationships · History / Time · Evolution · Cross-Team Reality · Decision / Evidence

FROM SOLO DEVELOPER TO CTO / CIO

Your responsibility changes. Your product does not have to.

NCT can contract to one person or expand across a team. The workspace is assigned by real responsibility, not by a hard-coded title. Whether you build alone or lead an organization, the same Canonical Engineering Reality can project the work surface you actually need.

Individual Developer (W1 · L1–L3 commonly surfaced) — Build, test, inspect Git, work with or without AI, preserve context and evidence without carrying organizational overhead. Daily build, test, Git, AI-assisted development, context and evidence
Tech Lead (W1 + W2 · L1–L4 commonly consumed) — Stay hands-on while seeing team execution, validation, evidence, quality, health and engineering gaps. Hands-on delivery + validation, team execution, quality and evidence
Principal Engineer (W1 + W3 · L1–L5 selectively consumed) — Continue building while working deeply with architecture, relationships, governance and system-level engineering reality. Implementation + architecture, relationships, system constraints and deep engineering
Engineering Manager / Director (W2 + W3 · L2–L5 commonly consumed) — Manage execution quality and engineering direction without being forced into the daily coding surface. Execution quality, health, risk, validation, team direction and governance
Enterprise Architect (W3 · L3–L5 commonly consumed) — Focus on architecture, boundaries, relationships, history, governance and cross-system evolution. Architecture, boundaries, relationships, history, governance and evolution
CTO / CIO (W2 + W3 · L3–L5 commonly consumed) — See delivery reality, risk, evidence, organizational governance and long-term engineering direction in the same system. Delivery reality, organizational risk, evidence, governance and long-term direction
Chief Architect (W1 + W2 + W3 · L1–L5 full-spectrum access when responsibility requires it) — When one person genuinely carries development, oversight and architecture responsibility, all three workspaces can coexist. Development, oversight, architecture and higher-order engineering reality in one system

Person → Small Team → Enterprise. One core, adaptive complexity, minimum necessary exposure.

CATEGORY DIFFERENCE

NCT is not trying to be another AI coding assistant.

This is a category framing, not a claim that every competing product behaves identically. Publish named competitor comparisons only after current factual verification.

AI helps create or edit code — AI participates inside a governed engineering reality
Context often centers on the current tool/session — Project memory is designed to outlive a task session
Model/provider can become the center of the workflow — Project is the subject; AI is a replaceable governed resource
Output may move quickly toward action — Candidate, evidence, authority and acceptance remain separate
Collaboration can optimize throughput — Independent analysis can optimize disagreement quality and verification
History is usually reconstructed from tool artifacts — NCT aims to preserve stable identity, references, evidence and relationships over time