Two ideas. Built in the open, validated in the open.

Two ideas, put up for scrutiny. Both are open core: the substance is Apache 2.0, and exactly one part of each could ever earn money. Whether it will is the experiment.

The questions validation has to answer

  1. 01

    How much of an idea must exist before it can be validated — and what does that cost in hours and focus?

  2. 02

    What is a realistic outcome — revenue, learning, or a clean no?

Findings will be published as the material matures. My network is part of the experiment: honest feedback is the point, and a no is worth more to me than a polite yes.

GuestGraph

guestgraph.io

Five strangers. One guest.

A guest books, checks in, eats, joins the wifi and leaves a review — and every system in the hotel stores someone different. GuestGraph resolves those strangers into one profile, and can always tell you why. A wrong merge is a data protection incident, so every decision is explainable and reversible.

For

Hospitality tech — hotels and hotel groups, and the PMS, POS and booking-system vendors that serve them.

  1. 01

    The engine

    Identity resolution — deterministic and probabilistic, layered by confidence, with a human review queue.

    built
    Open source
  2. 02

    The guest graph & API

    Immutable source records, a derived profile that can always be recomputed, everything reachable over REST.

    built
    Open source
  3. 03

    Explain, undo, audit

    Every merge answers “why?” and can be split again — an undo writes a permanent do-not-merge rule.

    built
    Open source
  4. 04

    Connectors

    Real PMS, POS and booking systems. Next on the roadmap — and the part that decides usability.

    next up
    Open source
  5. 05

    The hosted service

    Hosting, console, MCP for AI agents. One meter: billed per arrival — a number already on the hotel’s own dashboard. Planned, not open yet.

    model defined
    Commercial

Open core, because a black box that merges guests is not something I would deploy either.

CompanyGraph

companygraph.io

Everything a company knows. One graph.

What a company knows — roles, processes, metrics, rules, decisions — is written down, but no two people would look in the same place. So you ask a person instead; that is the tax. CompanyGraph is the structure that knowledge takes: a graph of Markdown, versioned like code, readable for people, reliable for AI.

For

Companies serious about using AI — anyone who wants agents acting inside their rules instead of guessing, from a company of one upward.

  1. 01

    The meta-model

    Core types, one schema per type — the vocabulary two companies that never met converged on. Published and versioned: core 0.4.1, eight types, every release tagged.

    vocabulary published
    Open source
  2. 02

    The graph of Markdown

    One page per thing, its title is its name, every reference by name — nothing points at nothing, nothing gets quietly lost.

    conventions published
    Open source
  3. 03

    The tooling

    A CLI with four commands — init, add, check, upgrade — that creates an instance, scaffolds from the schema, checks it mechanically and keeps it current with core. The CLI is specified and unbuilt. The three agent skills it was meant to install exist already — validate, add, export — and they are what keep the reference instance in shape. Open source, not the paid half of a free thing.

    skills built, CLI not
    Open source
  4. 04

    The talks, the example and a real instance

    Deck, PDF and audio in German and English, plus one worked example — and now a real instance rather than an invented one: 110 pages, public, checked against the conventions and drawn as a graph.

    real instance public
    Open source
  5. 05

    Consulting

    Building the model with you. One meter: billed per day, time and material — stop any time, everything stays yours.

    model defined
    Commercial

A model meant for people and AI at once must not cost more the more of them read it.

Both ideas open source · Apache 2.0