At its core, StandMeet is a foundation for audience-tailored introduction:
For any person — or thing — that carries multi-faceted information, it provides a tailored introduction to each specific audience that needs to understand it.
Not just a person. A company shows different faces to an investor, a job-seeker, and a passer-by. A product shows different faces to its contributors, maintainers, users, and investors. Same structure every time: one entity, many audiences, each needing a different slice.
An entity holds far more knowledge, across far more facets, than any single counterparty needs. So the channel by which someone comes to understand you can't be one-size-fits-all — it has to be tailor-made per audience, and that tailoring needs intelligence in the middle: either you introduce yourself every time (doesn't scale — dont-repeat-myself), or you place an agent there that knows your corpus and serves each asker the slice that's relevant.
Hence the name — StandMeet: a stand-in that goes to meet people for you. It does the meeting, the introducing, the answering — tailored to whoever's across the table — so you don't have to be there to repeat yourself.
For a person, concretely: an AI-readable mirror of you that talks to others in your own voice — a queryable, role-aware personal truth layer for a world where people increasingly ask an AI about you instead of asking you. Hiring is one current function on this foundation, not the product.
Inside this node
- product — why it exists & what it is
- requirements-to-design — the bridge: which product docs are still true, the spec-tag→design-doc→red-test pipeline, journey↔pillar traceability, and the orphan audit
- architecture — the stack and how it's built (seven pillars; obsidian-sync-mechanism and rendering-engines now live under the corpus pillar)