VÉRTICE Executive
Organises a priority opportunity or decision before — or at the start of — a material investment.
HOW TO READ THIS PLAYBOOK
A guide for turning a need into a well-defined delivery.
This playbook helps leaders and teams organise a working conversation. In a proposal, that conversation becomes scope, assets, responsibilities, acceptance criteria and clear exclusions.
EDAVEN guides Arcogi’s applied practice.Arcogi BoK brings together the criteria and practices guiding the work.Arcogi OS organises the operational components required by the agreed scope.Every initiative defines how work happens, when it is reviewed and how exceptions are handled.
ARCOGI AND THE PORTFOLIO
Arcogi can enter where your operation needs to move forward.
Some companies need to organise an opportunity. Others already have a case to execute or an operation that needs continuity. That is why our offers start at different points and connect when evidence supports the next move.VÉRTICE is useful when an organisation needs clarity before moving forward. When the case is already defined, another offer may be the better place to begin.
Decision Sprint
Turns a qualified case into action, evidence and a scale recommendation.
MDC / Expanded CoE
Co-manages or operates a persistent sociotechnical cell, from context to value capture.
Arcogi Academy
Builds the capability to operate, review and expand the practice.
OPERATIONAL CONTRACT FOR THIS CONTENT
An integrated, bounded and recoverable technical capability.
This content describes an applicable capability. In an engagement, scope, interfaces and acceptance criteria are agreed with the client.
Make the selected business case operable through agreed context, explicit accountability, controlled action and reviewable evidence.
One bounded case, with named owner, approved context, observable action and recorded review.
Teams use approved sources and agreed criteria before acting.
Applies only to the selected case and its agreed interfaces; it does not replace the client’s wider operating model.
Does not take material decisions, alter commitments or claim realised value without human authority and evidence.
Missing context, conflicting criteria or a material risk are recorded and escalated to the agreed owner.
The activity is paused or degraded to human review when context, authority or evidence is insufficient.
Work resumes only after correction, requalification and a recorded decision.
How it is structured
- frame the case, consequence and accountable owner
- establish context, interfaces, limits and dependencies
- demonstrate the slice, review it and prepare handoff
How it is verified
- scope, owner and advancement criteria are explicit
- expected and boundary behaviour can be demonstrated
- the client can accept, revise, pause or continue
Evidence that remains
- approved context and assumptions
- tests, decision record and traceable review
- version and learning record for the next cycle
Technical playbook
Integrated architecture for data, AI, agents, decisions and value.
Under the EDAVEN doctrine and operating movement, a technology-agnostic perspective guides integration into the client's chosen environment — with security, observability, cost and accountability embedded in the design.
01 · Architectural principles
Integrate before replacing. Qualify before automating. Preserve sovereignty.
Models and platforms can evolve
The architecture works with technologies selected by the client and avoids unnecessary dependency.
Data warehouses, lakehouses and other options remain valid
Data products can reside in the environment and storage approach defined by the organisation.
Material authority remains identifiable
Models and agents assist or execute only within boundaries proportionate to their impact.
Identity, access and reversibility are requirements
Protection does not depend on controls added after implementation.
Total cost follows the architecture
Data, models, infrastructure, oversight and operations are included in the value analysis.
Capabilities are introduced as needed
Each component can be adopted, integrated and extended without requiring a single large-scale transformation.
02 · Logical topology
The journey spans five domains and three cross-cutting capabilities.
SourcesERP · CRM · files · APIs · events
Data and semanticsproducts · metrics · contracts · quality
AI and agentsmodels · memory · tools · oversight
Decision and actionaccountable owner · target · deadline · execution
Value and learningeffects · costs · uncertainty · reuse
APIs · events · connectors · MCP where applicable
Experience for people and teams
Shared, governed knowledge
Integration, security and observability
MCP is treated as an open protocol for integration among models, tools and sources. It does not replace identity, authorisation, access policies or operational accountability.
03 · Data and semantics
Context is prepared as a product and delivered through contracts of meaning.
| Capability | Content | Typical integrations | Technical outcome |
|---|---|---|---|
| Data product | purpose, accountable owners, consumers, sources, granularity, quality, access, version, retention and refresh | data warehouses, lakehouses, databases, APIs, files and streams | usable, manageable context in the client's environment |
| Semantic model | entities, relationships, metrics, dimensions, hierarchies, calendars, units and formulas | catalogues, analytics engineering, BI and data platforms | consistent meaning across consumers |
| Semantic contract | definition, purpose, accountable owner, version, validity, change and limitations | metadata, APIs and catalogues | predictable, traceable use of definitions |
| Semantic layer | consumption interface with policies, versioning and access | BI, SQL, APIs, models, agents and applications | reuse of meaning without duplicating logic in every tool |
04 · AI and agents
Models are qualified for defined uses. Agents are authorised for bounded actions.
Purpose, performance, risk and cost
Temporal assessment, robustness, security, explainability, relevant bias, oversight, change and retirement.
Who or what is acting
A distinct identity, role, human owner, authorised tools and available context.
What may be recommended or executed
Least privilege, approval proportionate to impact, and financial and operational boundaries.
What may persist
Separation among temporary context, operational history and knowledge approved for reuse.
How activity is monitored
Activities, costs, performance, incidents, changes and material effects.
How to stop and recover
Suspension, access revocation, return to human execution and incident handling.
05 · Decision, action and value
A decision is managed as an operational object linked to time and consequence.
| Object | Minimum content | Use |
|---|---|---|
| Decision contract | question, accountable owner, alternatives, target, deadline, constraints, costs and reversibility | align business, technology and authority before execution |
| Action record | selected alternative, start date, operational owner, affected population and fidelity | distinguish the decision formulated from the action actually taken |
| Time-based monitoring | indicators, costs, deviations, incidents, adverse effects and interventions | continue, adjust, pause or reverse during execution |
| Value reconciliation | starting point, counterfactual, method, uncertainty, total costs and outcome | conclude positive, neutral, adverse or inconclusive value |
| Learning | context, validity, review, version, expiry and limitations | reuse knowledge without generalising beyond the evidence |
06 · Integration and implementation
Arcogi OS is designed to coexist with existing platforms and operate in the client's chosen environment.
The final form depends on data residency, security, scale, latency, cost and the technologies already adopted. Arcogi does not manage client data as an implicit part of the offering.
Snowflake, Databricks and equivalent ecosystems
Builds on catalogues, data products, semantics, AI and resources already available.
Data warehouses, databases and files
Adds contracts, integration and context without requiring prior migration.
APIs, events, connectors and MCP
Connects sources, tools, models and agents in a controlled way.
Cloud, VPS or authorised infrastructure
The topology is defined according to client requirements and contracted components.
Versionable configurations, knowledge and integrations
Reduces dependency and supports the evolution of models and vendors.
Monitoring, support and capability building
Defines who operates, who maintains and how future changes will be managed.
07 · Essential quality attributes
Security, observability, economics and resilience are part of the architecture.
Identity and least privilege
Segregation, secrets protection, encryption, logging, response and recovery.
Purpose and minimisation
Residency, retention, access, disposal and processing appropriate to the context.
End-to-end visibility
Metrics, events, activities, performance, costs and material incidents.
Costs by capability and use
Consumption of data, models, agents, infrastructure and oversight tracked from the design stage.
Failure without loss of accountability
Safe degradation, return to human action, recovery and continuity.
Integration without unnecessary dependency
Contracts, protocols and adapters compatible with technology evolution.
08 · Technical assessment
The technical buyer should be able to answer:
Where do data remain, and who administers each component?Residency, sovereignty, operations and responsibilities must be explicit.
How do metrics and definitions reach BI, AI and agents consistently?The model, contracts and semantic layer must be verifiable.
How are models and agents assessed, authorised, observed and retired?Purpose, risk, cost, identity, access and reversibility must be designed in.
How do decision, action and outcome remain connected over time?Accountable owners, dates, indicators, costs and interventions must form a comprehensible chain.
How does the architecture evolve without creating excessive dependency?Portability, integration contracts and model replacement must form part of the design.
09 · Technical artefacts and acceptance criteria
The artefacts describe and verify the solution; the commercial offering determines which ones are contracted.
Architectures, contracts, plans and records are technical outputs of delivery. They are not standalone offerings, nor do they imply that every component will be implemented in every engagement.
How the parts connect. VÉRTICE Executive is the OPTIONAL PORTFOLIO ENTRY. Verifiable delivery package is the contracted package delivered by Arcogi Services. The Prepared decision + continuity plan is the set of assets the client receives. The prepared decision completes the OPTIONAL PORTFOLIO ENTRY and marks the decision point for closing, correcting or qualifying a new engagement.
| Potential technical artefact | Verifiable content | Criterion or decision supported |
|---|---|---|
| Solution and integration architecture | Sources, consumers, components, information flows, integrations, responsibilities and non-functional requirements. | Fit with the environment, dependencies, boundaries and implementation impacts. |
| Data product specification | Purpose, sources, granularity, accountable owners, consumers, quality, access, refresh, retention and version. | Whether the required data can be produced and used with confidence. |
| Semantic model and metrics catalogue | Entities, relationships, dimensions, hierarchies, calendar, definitions, formulas, units and accountable owners. | Consistency of meaning across BI, analytics, models, agents and applications. |
| AI and agent qualification plan | Purpose, expected performance, material risks, costs, oversight, access, boundaries, monitoring and retirement. | Whether each use is ready for demonstration, implementation and monitoring. |
| Security and observability plan | Identity, authorisation, segregation, secrets protection, events, indicators, incidents, recovery and responsibilities. | How to protect, monitor, interrupt and recover operations. |
| Decision and value measurement plan | Question, accountable owner, target, deadline, alternatives, actions, baseline, indicators, costs, comparison and uncertainty. | How to connect execution, observed effect and the decision to continue. |
| Implementation, portability and transfer plan | Environments, components, integrations, operations, support, capability building, transition and technology evolution. | How to implement and evolve with sovereignty and controlled dependency. |
Arcogi BoK
Principles and patternsGuides the choices that apply to data, semantics, AI, agents, decisions, value, security and operations.
Arcogi ServicesContracted deliveryConducts discovery, architecture, integration, validation, capability building and transfer as defined in the proposal.
Arcogi OSProgressive materialisationOperational components are implemented only when included in scope, technically available and accepted.
The technical assessment clarifies artefacts, integrations and responsibilities without assuming the replacement of existing platforms or the availability of every component.
Applied cases
Explore the journey across sectors and functions.
These cases use synthetic data to demonstrate how the doctrine is applied. They do not represent a client implementation or client outcome.
© 2026 ArcogiEDAVEN is Arcogi's doctrine and operating movement.Outcomes depend on context, execution and the evidence available.
Arcogi Applied Casebooks
See the doctrine applied across six decision contexts.
Complete synthetic cases cover data products, semantics, people, AI, agents, decisions, time and value assessment without presenting them as client outcomes.