The agent in the boardroom
In July 2025, Kirin Holdings made room for a new participant in its Group Executive Committee: CoreMate. It was not a thirteenth decision-maker. It was an AI adviser built to test proposals and surface better questions before executives made the call.
Worked case · public-source reconstruction Autonomy: adviseWhy this case matters
A weaker version of the story would be “Kirin put AI in the boardroom.” The stronger reading is an operating-design choice: CoreMate was given a role, not authority. What appears to have mattered before it arrived were the decisions about what it would touch, what it would say, and where human judgement would stay in charge.
The case
In an executive committee, the valuable work often happens before anyone decides: a proposal is stress-tested, hidden assumptions surface, and weak options fall away. CoreMate is positioned in that moment. Proposal owners can spar with it before the meeting; executives can see selected discussion points during the meeting.
Kirin says CoreMate was built from ten years of Board and Group Executive Committee data, other internal materials, and the latest external information. Those materials are expressed through 12 AI personalities, each bringing a different management perspective.
That is why the case works as a canvas example. The model is not the story. The design of the role is the story: what CoreMate may see, what it may say, what it may never decide, and who remains accountable when its questions enter the room.
Why it matters
Without the canvas, CoreMate can sound like a quirky corporate AI story. With the canvas, the design question becomes sharper: what kind of participant are we creating, and where does that participant stop?
The operating model then snaps into view. CoreMate has cognition through the model, control through the meeting process and AI policy, and reach through the knowledge sources and display channels it can use. Its power comes from the combination, not from the model alone.
The filled canvas
The entries below are intentionally compact. A canvas should not read like a requirements document; it should make the load-bearing choices visible enough for a team to argue about them.
Worked example
What business outcome must this agent ultimately achieve?
Improve the quality and pace of Kirin Group executive decisions by adding source-grounded challenge before and during senior meetings.
Which workflow will it improve, and which metrics will show it worked?
Workflow: Group Executive Committee preparation and live deliberation. Metrics: proposal readiness, new perspectives surfaced, medium- and long-term discussion, decision cycle time.
01Who uses it directly, and who is affected by what it does?
Direct users: executives, proposal owners, facilitators, and secretariat. Affected: operating companies, employees, consumers, partners, shareholders, and society.
02What accuracy, explainability, speed, cost, and other standards must it meet?
Relevant, source-grounded, concise, and timely. Low-noise output is critical: only the strongest questions should enter a senior meeting.
03What information is available to support its work, and which sources should it trust?
Trusted context: ten years of Board and Group Executive Committee data, internal materials, management philosophy, proposal materials, and current external signals.
07What should it remember, what must it forget, and how will it improve over time?
Remember institutional records and approved feedback. Update external signals. Define what confidential meeting material is retained or forgotten.
08Who owns the outcome, who oversees the agent, and when must a person intervene?
Executives own decisions. Proposal owners and facilitators decide what enters the room. Governance sits with Kirin policy and management oversight.
09What to notice
CoreMate's most important design choice is not the model. It is the word “advise”: challenge, frame, and suggest, while executives keep decision rights.
Twelve personalities are useful only if the system filters them ruthlessly. The design problem is selecting the few questions that deserve the room.
The generic version is “an LLM in a meeting.” The valuable version is an LLM grounded in Kirin's history, proposal context, internal materials, and external signals.
Post-meeting feedback can make CoreMate better, but it also raises what should carry forward. Memory, access, and correction are design choices, not afterthoughts.
Coach audit
Not as an outside fact-checker saying “be careful,” but as an executive assistant asking the one question that matters: if CoreMate is going into the next senior meeting, what would make its questions worthy of the room? Here is what came back.
“How will you tell, after a meeting, whether the questions the agent raised actually improved the decision rather than just adding more talk?”The coach, on Target Workflow & Metrics (Cell 01)
Sources
Only public-source claims are treated as facts. Anything about internal thresholds, exact prompt-routing rules, or approval workflows should be read as a design implication unless Kirin confirms it.
More worked cases