Skip to main content

Org Simulation

@webframp/org-simulationv2026.09.15.1· 1d agoMODELS
01README

Agent-guided organization design simulation model inspired by the Curious Duck simulation studio (ducksimng.onrender.com). Capture an organization as a topology of teams, repos/modules, environments (with a defect/reliability model), and customer bases, wired together by connectors. Then run a deterministic, seedable flow simulation to estimate feature/bug cycle times, defect detection, find-vs-fix balance, and customer sentiment (NPS) under a chosen deploy policy.

Designed for organization design exploration: model the current org, model a proposed redesign, run both, and compare the versioned outcomes to decide whether a structural change is worth making. The agent interviews, the model simulates and persists.

02Release Notes

2026.09.15.1

Changed: Bump zod 4.4.3 → 4.6.5

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

03Models1
@webframp/org-simulationv2026.09.15.1org-simulation/mod.ts

Global Arguments

ArgumentTypeDescription
organizationContextstringBrief description of the organization, its size, business, and the team area under design
defectModelobjectGlobal defect-model parameters shared across all environments
fn design_topology(scenarioLabel: string, widgets: array, connectors: array, notes?: string)
Capture an organization design scenario as a topology of widgets and connectors, through structured conversation. AGENT GUIDANCE: You are modeling an organization the way the DuckSim studio (https://ducksimng.onrender.com/scenarios/studio) represents it: as a canvas of widgets wired together. Guide the conversation through these phases, and always confirm you're capturing either the CURRENT state (scenarioLabel: "current") or a PROPOSED redesign (a descriptive scenarioLabel like "split-platfor
ArgumentTypeDescription
scenarioLabelstringLabel for this topology snapshot — 'current' for the as-is org, or a proposed-design name like 'split-platform-team'
widgetsarrayWidgets on the organization canvas (teams, repos, environments, customer bases)
connectorsarrayWires between widgets
notes?stringContext about this snapshot — what it represents and why
fn run_simulation(scenarioLabel: string, seed: number, horizon?: enum)
Run the deterministic flow simulation against a previously-designed topology scenario. AGENT GUIDANCE: Before calling this, a topology must already exist for the given scenarioLabel (call design_topology first). This method reads that snapshot, runs a seedable simulation over the configured (or overridden) time horizon, and persists the results. The simulation approximates system dynamics, not a literal pixel-for-pixel replay of the DuckSim canvas: teams generate throughput based on skill, di
ArgumentTypeDescription
scenarioLabelstringWhich topology snapshot to run. Must match a label previously passed to design_topology, or 'current'.
seednumberRNG seed for deterministic, reproducible runs. Use different seeds to estimate variance.
horizon?enumOverride the topology's metrics.horizon for this run. Defaults to the topology's configured horizon.
fn record_design_decision(baselineLabel: string)
Record a design decision comparing a proposed scenario's simulated outcomes against a baseline. AGENT GUIDANCE: Before calling this, you should have run_simulation results for BOTH the baseline scenario (usually "current") and the proposed scenario, ideally with the same seed for a fair comparison. Read both simulation_results resources, compute the deltas (proposed minus baseline) for feature cycle time, bug cycle time, NPS, outstanding defects, and average certainty, and form a recommendatio
ArgumentTypeDescription
baselineLabelstringLabel of the baseline scenario results were compared against

Resources

topology(infinite)— Snapshot of an organization design scenario: widgets (teams, repos, environments, customer bases), connectors, and metrics config
simulation_results(infinite)— Outcomes of a deterministic simulation run against a topology scenario
design_decision(infinite)— Recorded decision comparing a proposed scenario's simulated outcomes against a baseline
04Previous Versions8
2026.08.28.1

2026.08.28.1

Changed: Normalized the extension license to Apache-2.0 and corrected the copyright holder to "Sean Escriva". Extensions that previously shipped an MIT LICENSE.md are now Apache-2.0, consistent with the repository root and every other extension. No code or behavioral changes.

Upgrade note: License text only. No API, schema, or runtime behavior changed.

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.3

2026.08.26.3

Fixed: Restored inline npm:zod@4.4.3 import specifiers so the registry quality scorer can resolve dependencies and score the extension. An earlier release used a bare "zod" import-map specifier, which published but scored as unscored.

Changed: Retained explicit compilerOptions.strict in deno.json. No behavioral or schema changes.

2026.08.26.1

2026.08.26.1

Fixed: Added missing description field to upgrade entry for version 2026.08.24.2. The omission caused swamp extension pull to fail with a catalog validation error ("upgrades.N.description: Invalid input: expected string, received undefined").

2026.08.24.3

2026.08.24.3

Added: Output metadata attributes for observability.

  • durationMs: Method execution duration in milliseconds.
  • collectedBy: Extension name that produced the data.
  • fetchedAt: ISO 8601 timestamp when data was fetched (added to resources that previously lacked it).
2026.08.24.2

2026.08.24.2

Added Troubleshooting section documenting design_topology prerequisite, duplicate widget ID validation, connector reference validation, defectModel configuration, and complex nested input guidance.

2026.08.21.2

2026.08.21.2

Changed:

  • design_topology now rejects a topology with duplicate widget ids, with an error listing the offending id(s). Previously duplicate ids passed validation and silently collapsed to whichever widget was listed last once the simulation indexed widgets by id, producing a topology that simulated differently from the one you described.
2026.08.21.1

2026.08.21.1

Changed: Added .describe() to the eight cosmetic spawn/despawn region bounds on the customer base config schema (startsXMin/startsXMax/ startsYMin/startsYMax/stopsXMin/stopsXMax/stopsYMin/stopsYMax), clarifying that they are informational only and not used by the simulation. No behavioral change.

2026.07.23.1

Added: Initial release of @webframp/org-simulation, an agent-guided organization design simulation model inspired by the Curious Duck simulation studio (ducksimng.onrender.com).

  • design_topology — capture an organization as a topology of teams, repos/modules, environments (with a defect/reliability model), and customer bases wired by connectors, under a named scenario label ("current" for as-is, or a descriptive label for a proposed redesign).
  • run_simulation — run a deterministic, seedable flow simulation against a topology scenario, estimating feature/bug cycle times, defect detection and find-vs-fix balance, customer sentiment (NPS), and environment reliability over a configurable time horizon.
  • record_design_decision — record an adopt/reject/iterate/hold decision comparing a proposed scenario's simulated outcomes against a baseline, with quantified deltas and risks the simulation can't capture.

Three resources track the model's data: topology, simulation_results, and design_decision, each versioned per scenario/seed/comparison.

2026.07.23.1

2026.07.23.1

Added: Initial release of @webframp/org-simulation, an agent-guided organization design simulation model inspired by the Curious Duck simulation studio (ducksimng.onrender.com).

  • design_topology — capture an organization as a topology of teams, repos/modules, environments (with a defect/reliability model), and customer bases wired by connectors, under a named scenario label ("current" for as-is, or a descriptive label for a proposed redesign).
  • run_simulation — run a deterministic, seedable flow simulation against a topology scenario, estimating feature/bug cycle times, defect detection and find-vs-fix balance, customer sentiment (NPS), and environment reliability over a configurable time horizon.
  • record_design_decision — record an adopt/reject/iterate/hold decision comparing a proposed scenario's simulated outcomes against a baseline, with quantified deltas and risks the simulation can't capture.

Three resources track the model's data: topology, simulation_results, and design_decision, each versioned per scenario/seed/comparison.

05Stats
A
100 / 100
Downloads
0
Archive size
40.7 KB
  • Has README or module doc2/2earned
  • README has a code example1/1earned
  • README is substantive1/1earned
  • Most symbols documented1/1earned
  • No slow types (deprecated)1/1earned
  • Dependencies pass trust audit2/2earned
  • Has description1/1earned
  • Platform support declared (or universal)2/2earned
  • License declared1/1earned
  • Verified public repository2/2earned
06Platforms
07Labels