jc10.ai
EN ES
Get updates

The orchestrated IDE for data and AI

From the business case to the last line of code.

jc10 is an engineering system for developers and architects who build with data and AI. An IDE where AI agents work side by side, and a conductor that plans the work, tracks every job and proves it before it ships.

Get updates

Nothing to buy. A working system for people who care how enterprise software is built. Windows 10 and 11, one exe.

The model proposes. The contract decides.

Every piece of work in jc10 sits in one chain. Nothing is outside it.

  1. Constitutionthe rules
  2. Business groupwhy
  3. Solutionwhat
  4. Programhow
  5. Planthe case
  6. Taskthe work

000_constitution

The contract decides.

AI agents are fast, and speed without rules is risk. In jc10 every agent session reads one short constitution before it does any work. The model proposes. The contract decides.

  1. Folders. Every business group, solution and program has a number. Numbers are never reused. The registry is the map.
  2. Work. Edit, build, test, certify, release. In that order, every time.
  3. Machines. Each job runs on the machine named for it. Builds never run where people work.
  4. Certified. Only reviewed, fingerprinted and signed extensions are installed. A revoked one is turned off.
  5. Evidence. Every ask is a task, and a task is done only with evidence attached.
  6. Safety. No secrets in any repo. Production waits for the human's explicit go. These rules do not bend.
  7. Public. Every public page is in English and Spanish, and tells search engines and AI models exactly what it tells people.

000_registry

One map for everything.

Governance starts with knowing what exists. Every part of jc10 has a place, a number and an owner, and the registry is the single map of it.

jc10
├─ 000_constitution           # the rules
├─ 000_registry               # the map
├─ bg01_ide                   # business group
│  ├─ sol001_ide              # solution
│  │  └─ 011_jc10_ai_ide      # program         live
│  └─ sol002_extensions
│     └─ 021_jc10_jira        # program         planned
├─ bg02_quality
│  └─ sol003_certification
│     └─ 012_jc10_devbench    # program         live
├─ bg03_identity              ... 031_jc10_sso    planned
└─ bg04_experience            ... 041_jc10_shell  planned
Business groupWhy. The business outcome it serves. This is where finance and the enterprise decide.
SolutionWhat. The capability that delivers the outcome. This is where architecture lives.
ProgramHow. One repo, one build, one owner. This is where data, AI and code live.

anly_plans

Every plan sees the full line.

Most tools cover one layer. A jc10 plan holds all of them at once, so a decision at the top can be traced to the code that carries it out, and back.

One ask, traced top to bottom.

1item          "Tiered pricing for EU customers"
2finance       business case: revenue, cost of change, risk
3enterprise    owners: sales ops, billing  # four countries
4architecture  pricing service, price table, audit log
5data_ai       price history load, margin check per tier
6code          3 jobs on 2 machines, tests, one review
7evidence      attached to the item  # nothing done without it
8release       test channel, then stable, after your go
  1. FinanceThe business case: revenue, cost and risk.
  2. EnterpriseHow the business really runs: processes, teams, countries.
  3. ArchitectureThe plan that joins them: systems, data flows, security.
  4. Data and AIA solid data foundation first, then models and agents on top.
  5. Code and machinesThe detail: builds, tests, servers. Every millisecond matters.

bg01_ide / sol001_ide / 011_jc10_ai_ide

The IDE.

One Windows exe. An editor, terminals and many AI agent sessions in one window, with your data tools beside them.

  • Agents side by side. Each session has its own terminal and its own job. You watch them all at once.
  • Sessions that last. Sessions survive restarts and pick up where they stopped.
  • Data in the same window. SQL and data tools next to the agents. Jobs run on the machine where the data lives.
  • One sign-in, two channels. Sign in once. Updates arrive through a test channel and a stable channel.

tasks

Every ask is a task.

A conductor session plans the work and drives a team of agent sessions across your machines. Every ask gets a number, an owner and a status, and it is done only with evidence.

id          J10-A112
status      done
owner       conductor
source      "Tiered pricing for EU customers"
evidence    tests 128 passed, review 0 findings,
            data checks ok, go given
  1. 1

    Plan

    You ask in plain words. The conductor writes the plan and splits it into tasks.

  2. 2

    Run

    Agent sessions claim the tasks on the right machines, in parallel, in view.

  3. 3

    Prove

    Tests, reviews and checks are attached to each task. A failed check blocks it.

  4. 4

    Release

    After your go: test channel, then stable. Rollback is one step.

bg02_quality / sol003_certification / 012_jc10_devbench

Built so you can trust it.

Quality is its own business group, not an afterthought. Good engineering is rules you can check.

  • Certified extensions. Every extension is reviewed, its exact package is fingerprinted, and the list is signed.
  • Secrets stay sealed. You type a password once into the vault. Agents use it by name and never see it.
  • Your go for production. Changes to live systems wait for your explicit yes.
  • Your machines, your data. Work runs on your own computers and servers.

arc.jc10.ai

The hub.

arc.jc10.ai is where you sign in, get the IDE and receive its updates. One account for the hub and the IDE.

  • Sign in once. The same account opens the hub and the IDE.
  • Get the IDE. The Windows installer comes from the hub.
  • Updates you can trust. Every build goes to the test channel first, then to stable.
  • Your apps in one place. The launcher for the jc10 apps you use.

updates

Follow the build.

A short note when something real ships: a new release, a new rule, a new part of the system. Nothing to buy, and you can leave with one click.

about

Why jc10 exists.

20+ years across web, software, data and AI, in 8 countries, from P&L decisions down to databases and code. The hard part was never one layer. It was keeping the layers connected, and governed.

jc10 is the system Juan runs his own engineering on, every day. Governance-driven: the model proposes, the contract decides, and nothing counts as done without evidence.

Juan CardenaEnterprise Architect, Data and AI
Problems 0OutputTerminal

jc10 conductor ready. Constitution loaded. Press Trace a run to follow one ask from plan to release.

>

Get jc10 updates

A short note when something real ships. Nothing to buy.