研究システム · 日付付きエビデンス
プロダクト、アーキテクチャ、エビデンス、ガバナンスの判断をソースコードで検証する自社研究システム。
これらの構築物は、コンサルティング上の問いを検証可能なシステムへ変えます。権限がどこにあるか、どのエビデンスがゲートを進めるか、モデルをどう制限するか、何が未証明かを示します。各詳細ページは、実装済みソース、文書化された設計、導入エビデンスを区別します。
Category spine · 03 systems
LaunchpadOS codifies product judgement. Auralink pressure-tests it against a Physical AI system. TransformationOS carries the resulting decisions into portfolio, operating-model, and Agile-at-scale work.
01 · Category operating system
Source toolkit under active development
Source through 2026-08-25
Makes full-lifecycle product judgement versioned, inspectable, and executable.
Product decision
Define which product decisions matter, which evidence advances a gate, who owns the call, and what must cause the decision to reopen.
Technical record
Versioned skills, the Operated Product Decision Graph, Release Case boundaries, CLI and MCP surfaces, workflow state, evaluations, and audit records.
02 · Physical AI reference implementation
Documented research reference
Source through 2026-08-24
Pressure-tests product and architecture decisions against a real cross-domain Physical AI source system.
Product decision
Separate the reusable horizontal coordination substrate from vertical protocol ownership and keep final safety authority with the local controller.
Technical record
Signed proposals, resource leases, policy and admission boundaries, local veto, authoritative readback, catalogues, conformance paths, and cross-domain simulation.
03 · Organisational transformation demonstrator
Demonstration platform
Source through 2026-04-08
Connects portfolio intent, product operating models, Agile@Scale, delivery evidence, and governance decisions.
Product decision
Represent decision rights, assumptions, approval states, evidence, cadence, and handover across the transformation portfolio.
Technical record
Tenant configuration, workflow modules, connector boundaries, retrieval, DORA and flow metrics, scenario records, proposal-first writes, approvals, and audit state.
Capability experiments · 07 source systems
Each experiment isolates a hard product boundary—from embedded telemetry and security scanning to regulatory evidence, agentic workflows, diligence, and creative orchestration.
Public early release
A Rust static-analysis tool focused on AI-generated and AI-application code patterns. It combines tree-sitter parsing, source-controlled rules, SARIF output, command-line and editor surfaces, and optional model-assisted triage.
検証領域： ガバナンス信頼性
Development prototype
A regulatory-workflow backend prototype with inventory, retrieval, classification, evidence, remediation, audit, and report modules. It is a decision-support system under development, not legal advice or a conformity assessment.
検証領域： ガバナンスデータ
Development prototype
A multi-tenant business-workflow prototype with departmental modules, queued agent execution, retrieval memory, and model routing. The source demonstrates orchestration boundaries, not autonomous business operation.
検証領域： アーキテクチャデータ
Development prototype
An SME assessment and reporting prototype combining conversational intake, deterministic scoring, country data, retrieval, and a Mistral-assisted report pipeline. It is guidance software under development, not a legal determination.
検証領域： ガバナンスデータ
Development prototype
A full-stack diligence-workflow prototype with deal, research, scoring, portfolio, and reporting surfaces. Its source demonstrates workflow architecture and provider abstraction; it does not establish investment performance.
検証領域： データアーキテクチャ
Development prototype
A multi-surface creative-workflow prototype with web, API, gateway, worker, mobile, and document-add-in packages. The repository shows routing and workflow structure; provider availability and output quality are configuration-dependent.
検証領域： アーキテクチャ統合
Source prototype with software and firmware boundaries
A vehicle-data prototype spanning API, user surfaces, embedded source, and a Rust signal-normalisation core. The implemented record supports trace and fixture work; vehicle, hardware, and fleet validation remain outside it.
検証領域： 統合アーキテクチャ
Evidence doctrine
Name the customer, economic, portfolio, and operating constraint.
Record the choice, owner, evidence threshold, and invalidation rule.
Express the decision in architecture, source, interfaces, and assurance work.
Return field and delivery evidence to strategy, scope, funding, and governance.