. . . . . . . . . . ..::--==++==--::.. ..::--==++==--::.. . . .:-=+**##%%%%##**+=-:. .:-=+**##%%%%##**+=-:. ..:-=+*#@@%%##**++==--:. .:--==++**##%%@@#*+=-:.. .:-=+*#%%#*+=-:.. ..:-=+*#%%#*+=-:. .:-==--:. route map ship .:--==-. . +------+ +------+ . . . . | data |--+--| work | . . . +------+ | +------+ . ..::--==++==--::.. | ..::--==++==--::.. . .:-=+**##%%%%##**+=-:. | .:-=+**##%%%%##**+=-:. . . +- policy + proof . .

Research and education companion for the open framework

Learn the method through real workflows.

AI Dev Days researches, teaches, and pressure-tests approved AI-Native Operating Framework concepts through public sources, real workflows, talks, labs, scenarios, and workshops.

Bring AI Dev Days to your team Inspect AI Dev Days material

Companion role

Research the work. Teach the method. Return what is learned.

AI Dev Days maintains a clear boundary between framework authority, education material, implementation choices, and observations from practice.

Research

Trace public sources, real operating questions, implementation choices, and observed limits without promoting raw findings into framework core.

Education

Turn approved framework concepts into talks, labs, scenarios, facilitator material, and workshops built around work people need to improve.

Feedback

Return questions and evidence through explicit review. Practice may inform a proposal; only framework governance changes framework core.

How it works

A practice system for operating work.

Participants work from a real scenario or workflow, make the operating standard visible, and test the handoffs, decisions, controls, and recovery paths.

Start with the work

The workflow is the workshop.

Bring a recurring process, a difficult handoff, or an operating decision. The session turns it into something the team can understand, practice, and improve together.

What participants learn

Make the work clear enough to perform and improve.

Define the recurring business work before choosing a tool.

Make responsibility, authority, controls, evidence, and exceptions explicit.

Write standards and SOPs that people and AI can use under accountable ownership.

Separate framework concepts from tool-specific implementation choices.

Review the result, identify open questions, and decide what should change next.

Formats

Use the format that matches the decision.

Choose a talk, technical session, hands-on workshop, or executive seminar based on the audience, workflow, and learning outcome.

Talk

A concise framework-first briefing built around a real operating problem and the decisions it exposes.

Technical session

A deeper walkthrough of how the method applies to a specific workflow and technology environment.

Hands-on workshop

Scenario-driven practice that turns a real workflow into clearer standards, roles, controls, evidence, and handoffs.

Executive or corporate seminar

A facilitated operating-model session for leaders responsible for adoption, governance, capability transfer, and risk.

Learning ladder

From individual repeatability to ecosystem interoperability.

Build the capability from one person’s recurring work to shared operating practices across teams, organizations, and partners.

01
Individual
Repeatable work
Make one person’s recurring work explicit enough to review, repeat, and improve.
02
Team
Coherent handoffs
Clarify shared standards, ownership, decisions, evidence, exceptions, and handoffs across a team.
03
Organization
Governance and visibility
Connect business standards, SOPs, authority, controls, and review cycles across functions.
04
Ecosystem
Interoperable ways of working
Preserve shared operating meaning across partners, tools, and organizational boundaries.

Bring AI Dev Days to your organization.

Start with the audience, the operating pressure, and the workflow people need to understand. Digital Meld will shape the session around the decision your team needs to make.

Discuss AI Dev Days Inspect the framework