BAKEOFF
SERVICE CONTRACT · VIEW: GOV
Axiom
BAKEOFF is a governed provider evaluation with BedaSoftware. Ilya built the FHIR stack. Yana runs the company. The i18n scope is 47,430 COIN. Every bakeoff criterion scored. Every COIN commitment governed.
Constraints
MUST: Evidence every meeting with timestamp + attendee + medium MUST: Govern all contacts as INTEL vitaes (Ilya Beda CTO, Yana Beda CEO) MUST: Track bakeoff evaluation criteria with scored evidence MUST: Govern COIN commitments for i18n translation scope MUST: Map BedaSoftware capabilities to IHI Call 12 addressable budget (€6.5M) MUST NOT: Disclose VAULT-gated terms in SHOP surfaces MUST NOT: Mint COIN without governed work evidence
Capabilities
BAKEOFF_EVALUATE, COIN_GOVERN, CONTACT_GOVERN, MEETING_EVIDENCE
privacy: VAULT
COVERAGE:
SPEC
Purpose
BedaSoftware — provider evaluation for EU deployment partner. FHIR R4/R5 backend, i18n translation of CANONIC books, COIN-governed work.
BedaSoftware (Ilya Beda CTO, Yana Beda CEO) built the FHIR stack underpinning MammoChat, SkinIQ, and the clinical pipeline [X-91][X-92]. 1,174 governed commits from Ilya across 8 Hadley Lab projects. The deal evaluates BedaSoftware as CANONIC’s deployment partner for EU i18n translation (Russian, Arabic, Spanish, German editions of both books) and IHI Call 12 [X-59] technical delivery.
Deal Stage
PROSPECT → QUALIFY → PROPOSE → [NEGOTIATE] → CLOSE → LEDGER
↑
CURRENT STAGE
Entity
| Field | Value |
|---|---|
| Legal Name | BedaSoftware |
| Type | FHIR development firm |
| Principals | Ilya Beda (CTO), Yana Beda (CEO) |
| Operations | USA, Canada, New Zealand, Israel, Germany, Switzerland |
| History | 1,174 governed commits (Ilya), 94 governed commits (Yana) across Hadley Lab |
i18n Scope
CANONIC DOCTRINE (49 chapters)
├── Russian edition — 12,495 COIN ceiling
├── Arabic edition — TBD
├── Spanish edition — TBD
└── German edition — TBD
CANONIC CANON (44 chapters)
├── Russian edition — 11,220 COIN ceiling
├── Arabic edition — TBD
├── Spanish edition — TBD
└── German edition — TBD
TOTAL CEILING: 47,430 COIN (all languages, both books)
IHI Call 12 Addressable Budget
BedaSoftware-addressable scope: €6.5M [X-59]
├── WP3: CANONIC Governance Framework — €2.0M (technical delivery)
├── WP5: Multi-site Validation — €2.5M (deployment)
├── WP6: Dissemination & Exploitation — €700K (i18n)
└── WP7: Ethics & Data Protection — €500K (compliance)
Routes
web_docs: https://hadleylab.org/
web_surface: https://hadleylab.org/DEALS/BAKEOFF/
magic: magic://hadleylab.org/DEALS/BAKEOFF/
INTEL
Vitaes
Ilya Beda
| Field | Value |
|---|---|
| Name | Ilya Beda |
| Title | CTO, BedaSoftware |
| ir4y.ix@gmail.com | |
| Commits | 1,174 governed commits across 8 Hadley Lab projects (STARGEO, SkinIQ, Dr.Moonlight, UCFWealth) [X-91][X-92] |
| Expertise | FHIR R4/R5 backend architecture, HL7 [X-61], clinical data systems |
| Signal | TECHNICAL CORE: Built the FHIR stack. Knows the codebase better than anyone outside Dexter. Russian speaker — first i18n language. |
Yana Beda
| Field | Value |
|---|---|
| Name | Yana Beda |
| Title | CEO, BedaSoftware |
| troublegirl007@gmail.com | |
| Commits | 94 governed commits across 5 Hadley Lab projects |
| Expertise | Apple/iOS surfaces, business operations, Dubai expansion |
| Signal | BUSINESS LEAD: Runs BedaSoftware operations across 6 countries. Dubai expansion = Arabic i18n bridge. |
Evidence Chain
| Layer | Source | Status |
|---|---|---|
| 1 | Git history: 1,174 + 94 governed commits | VERIFIED |
| 2 | DECK-TALK-ILYA-YANA.md (2026-03-12) | AUTHORED |
| 3 | WORK-TALK-ILYA-YANA.md (2026-03-12) | AUTHORED |
| 4 | IHI Call 12 budget mapping | LINKED |
LEARNING
Trail
| Date | Event | Insight |
|---|---|---|
| 2026-03-12 | DECK-TALK and WORK-TALK authored | Positioned BedaSoftware as EU deployment partner with i18n scope |
| 2026-03-19 | Yana + Ilya reading DOCTRINE | Book study is self-initiated certification pre-work. Deal stage advanced to NEGOTIATE. |
| 2026-03-19 | Both confirmed for 3/20 call | Yana inviting Ilya. Calendar accepted. GoRunner demo sent same day. |
| 2026-03-19 | CaribChat pipeline surfaced | Trinidad/Caribbean deployment mentioned as near-term BedaSoftware opportunity |
ROADMAP
VOCAB
| Term | Definition |
|---|
INHERITANCE CHAIN
DEAL
DEAL governs relationships. Every deal ledgered. Every stage evidenced.
MUST: Ledger all deal events MUST: Link to governed contacts MUST: Evidence every stage transition MUST: Every child instance at DEALS/ inherits these constraints MUST: Instance trees carry all state (CANON, INTEL, LEARNING, COVERAGE, ROADMAP, VOCAB) MUST NOT: Store secrets in public surfaces MUST NOT: Hardcode deal names in law MUST NOT: Nest instance directories under SERVICES/DEAL/ (service contract is the class, not the instance)
SERVICES
SERVICES compose primitives — INTEL + CHAT + COIN. Every service governed. Every scope discovered.
MUST: Maintain TRIAD integrity (CANON.md + VOCAB.md + README.md)
MUST: Treat SPEC as scope identity (`{SCOPE}` directory), not as a file
MUST: Every SERVICE scope include ROADMAP.md, COVERAGE.md, LEARNING.md, and `{SCOPE}.md` as governed content surfaces
MUST: Discover SERVICE scopes from filesystem only (no manual catalog)
MUST: Keep http:// and magic:// on the same namespace (transport differs, scope path matches)
MUST: CANON.md = axiom + universal constraints (no service names, no paths, no implementation)
MUST: README.md = how to run the CANON (nothing else)
MUST: {SCOPE}.md = SPEC — the interface (purpose, routes, projections, ecosystem)
MUST: SHOP.md = public projection file (per scope, filesystem-discoverable)
MUST: VAULT.md = private projection file (per scope, filesystem-discoverable)
MUST: Runtime implementation remains under ~/.canonic; this workspace is governance-first
MUST NOT: Hardcode service names in CANON constraints (law speaks universals)
MUST NOT: Define ungoverned terms outside VOCAB.md
MUST NOT: Treat `{SCOPE}.md` as SPEC identity
MUST NOT: Move architecture/lifecycle into README
MUST NOT: Leak private projections to public surfaces
MUST NOT: Maintain duplicate mapping tables outside generated manifest outputs
MUST NOT: Add runtime jargon to governance contracts
MUST: Ledger-consuming services declare source ledgers, scope filters, and closure gates
MUST: Learning governance remains live — closure claims require fresh DISCOVER → GENERATE → RELINK evidence
hadleylab-canonic
HADLEYLAB ships software. Every app, book, paper, deal, and patent is PROOF that MAGIC works. COIN = WORK. LEARNING = COMPUTE.
MUST: Every app, book, paper, deal, or patent is evidence of MAGIC MUST: All scopes inherit canonic-canonic/CANONIC.md governance MUST: All users governed under USERS/ via SERVICES/USER MUST: Cross-index INTEL across users (INTEL.md) MUST: Shared events propagate to ALL affected user dashboards MUST: Maintain governance workspace purity (.md files only) MUST: Ledger all COIN (validated work) through MAGIC 255 MUST: Compile all INTEL from governed sources MUST: Keep frontend/runtime implementation under ~/.canonic (hidden runtime) MUST: Surface governed TALK, Library, and SERVICES scopes (no orphan content) MUST: Derive nav labels from governed scope names (no hardcoded strings) MUST NOT: Publish without governance (CANON.md required) MUST NOT: Duplicate primitives — compose from INTEL, CHAT, COIN MUST NOT: Silo intelligence inside a single user when multiple are affected MUST NOT: Expose VAULT contents outside NDA scope MUST NOT: Store runtime artifacts in governance workspace
canonic-canonic
SPEC is governance. `canonic-canonic/` is the spec root.
MUST: Keep this repo governance-only (.md/.pdf) MUST: Publish workspace mapping in CANONIC.git (no hardcoded repo lists) MUST: Preserve three primary lanes: FOUNDATION, INDUSTRIES, MAGIC MUST NOT: Commit runtime artifacts here (runtime belongs in ~/.canonic/) MUST: Sell MAGIC tiers — the product, not the proof (proof is hadleylab-canonic) MUST NOT: Embed beta-test app URLs in platform page content