What is Taste Engineering?
Your AI today is running on someone else's judgment.
Raw data doesn't reason. And AI decides like the median of everyone. Now your custom taste can sit in front of every model, vendor, and tool you run to help you make decisions that you can trust.
A generic model and a taste model answering the same call, side by side.
Every decision is a combination of principles, precedents, pressures, and aesthetics. Edin captures and codifies it all into one layer, maintains it as your thinking changes, and secures it.
What your company will not do under any condition. Your bedrock values, machine-readable, human-generated.
How your company reasons over time against your values and decision patterns. Version-controlled and diffable, like rings of a tree.
Per team, per function, per market. Branches are allowed to grow in various directions and disagree with each other. Trunk and roots resolve the conflict.
The current state — recent decisions, live exceptions. Regenerated frequently by design as what's best next quarter is always changing.
Built on your company's data, decisions, and rejections — not on the average of everyone.
Your taste model should outlive every vendor in your stack and be yours to own.
Every decision your company makes should generate smarter and faster ones in the future.
Taste is a garden that requires tending. Our proprietary harness includes in person diagnosis, capturing decision exhaust across all your departments, workflow mapping, and retrieval resolved into weights your AI systems can run on.
Every build is measured against decisions the model never saw.
We send Taste Engineers to you to be in the room to document scenarios where your people make the tough decisions.
We pull seamlessly from where decisions already happen — Slack, mail, Drive, deal files, tickets.
Principles ranked, conflicts resolved, machine-readable. This is what the layer runs on.
Where your corpus lives and the record of everything it decided.
Pricing exception — enterprise renewal
Held · contradicts Root 02 · agent-salesDiscount authority — Marketing vs. Finance
Branch conflict · unresolved 2d6 review calls disagree with your people
Drift · Trunk 04, Trunk 09| Department | Reads | Writes | Signers |
|---|---|---|---|
| Finance | all | Roots | 2 |
| Product | Roots · Trunk | Branches | 3 |
| Operations | Roots · Trunk · Branches | Leaves | 4 |
| Marketing | Trunk | none | — |
| Action | Verdict | Principle | Agent | |
|---|---|---|---|---|
| Vendor renewal · 3-year term | approved | Trunk 07 | agent-procure | 14:22 |
| Discount beyond floor | refused | Root 02 | agent-sales | 14:19 |
| Candidate offer · band 4 | approved | Branch 11 | agent-people | 14:11 |
| Data-sharing clause | refused | Root 01 | agent-legal | 13:58 |
| Campaign claim copy | approved | Trunk 12 | agent-brand | 13:47 |
| Supplier change · sole source | refused | Root 04 | agent-procure | 13:31 |
Pricing exception — enterprise renewal
Held · contradicts Root 02 · agent-sales · 41mDiscount authority — Marketing vs. Finance
Branch conflict · unresolved 2d · 2 signers needed6 review calls disagree with your people
Drift · Trunk 04, Trunk 09 · flagged by monthly eval| Department | Reads | Writes | Signers | Last change |
|---|---|---|---|---|
| Finance | all | Roots | 2 | 11 Mar |
| Legal | all | Roots · Trunk | 2 | 4 Mar |
| Product | Roots · Trunk | Branches | 3 | 28 Feb |
| Operations | Roots · Trunk · Branches | Leaves | 4 | 2 Mar |
| Marketing | Trunk | none | — | — |
| Actor | Action | Object | |
|---|---|---|---|
| d.okafor | signed | Root 04 — sole-source supplier | 11 Mar 09:14 |
| agent-legal | refused | data-sharing clause · Root 01 | 11 Mar 08:52 |
| m.reyes | overrode | Branch 11 · one-time, reason logged | 10 Mar 17:20 |
| system | rebuilt | Leaves · 1,240 weights | 10 Mar 03:00 |
| k.lund | revoked | Marketing write scope | 8 Mar 14:06 |
| Inference | on-prem · us-west |
| Egress | none — no content leaves the perimeter |
| Identity | SSO · SCIM provisioning |
| Roots writes | 2 named signers required |
| Retention | your policy, enforced at write |
| Export | open formats, on demand |
| Audit | append-only · 1,204 entries |
Overview — what the layer decided, what it refused, and who is allowed to change it.
Decisions land here as they're made. Inside your perimeter, structured on arrival.
Ask your own record. What did we decide, when, and on what grounds, answered from your corpus instead of guessed by someone else's AI.
Authentication and authorization on every read and write, scoped by team, function, and seniority.
Every verdict logged with the principle behind it, and a running picture of what your company decides and where it's drifting.
Intelligence accelerates monthly. Models deprecate every quarter. Your taste grows with every action and every piece of feedback. We architect the layer that outlasts all of it and the credentials your agents carry when they meet someone else's.
Left, agents proving who they are. Right, the record you own.
APIs and MCP. Agnostic to model, vendor, and tool.
An action that contradicts your company gets stopped, logged, and sent back to a human.
Local inference, private retrieval. We never take custody of your material. This is your garden.
Your agents will transact with other companies' agents. Both sides need proof that the other is who it claims, and that it acts on judgment its company actually signed. Your taste layer is that credential.
Owning your data was never the point. Data ages, and alone it decides nothing.
A record of what happened cannot tell a machine what to do next. The reasoning sitting on top of it can — which projects you pass on, which exceptions you grant, which corners you never cut. That layer is the asset, and almost no company has ever written it down.
Edin builds your taste layer, maintains it as your thinking changes, and leaves it secure in your hands. It plugs into any model, vendor, or tool you run, and it evolves as your company does.
hello@edincloud.com