The reference
core.
The site describes an offline acceptance test on synthetic data. The scope is the core: not the whole service, and not proof of effectiveness in the field.
For IT departments and assessment leadsBefore saying yes,
Before saying yes,
let’s look inside.
Where do the data run? Which components are available? Who is accountable for what? A first assessment should start from these questions, not from a promise.
A document to share (in Italian)The pre-assessment
The pre-assessment
sheet.
Scope, logical architecture, technical questions and checks to complete. It is not a certification of the system.
The reference
The service
in your environment.
Hosting, models, access, integrations, retention and support must be specified in the actual proposal.
The illustrative
experiences.
This site does not run models or receive files: it only sends requests for a first conversation. The walkthroughs illustrate the method and its reports.
Source for the core: the COGI.CO site, consulted on 6 October 2026, which reports protocol v11.1 and an acceptance test on 1 October 2026. No independent review of the code has been carried out.
Distinct components.
Explicit responsibilities.
This diagram is an editorial representation of the logical architecture, not a verified deployment topology. It helps distinguish what needs to be analysed in the proposed configuration.
LOGICAL ARCHITECTURE / SUMMARY FOR ASSESSMENTConceptual diagram
01
People and responsibilities
Question, mandate, oversight and final choice.
02
Method and facilitation
Organising the discussion and criteria for the report.
03
Represented perspectives
Sources, remit, limits and conditions for challenge.
04
Core and memory of the discussion
Composition, logs and traceability to be documented.
05
Models and external services
Dependencies, data flows and conditions for replacement.
06
The organisation’s environment
Access, integrations and operations to be defined.
An essential distinction. The fact that the core runs offline does not mean that the interface, models, integrations and service operations are all available offline.
No box ticked
with a reassurance.
Each item needs an answer that refers to the configuration, someone responsible and, where relevant, verifiable evidence.
AreaWhat to verify
Hosting and location
Where do the interface, core, models and logs run? Which suppliers or sub-suppliers are involved, and in which environments?
Information flows
Which data come in, are processed, are possibly sent to external services and are returned? A map is needed for each component.
Models and dependencies
Which models are planned? Which data do they receive? What are the conditions for replacing them, the operational consequences and the costs?
Identity and authorisation
Which access rights, roles and controls are actually implemented? How are use, modification and export of information authorised?
Retention and deletion
Which data and logs are retained, for how long, and with which procedures for deletion, export and verification?
Integrations and operations
Which systems need to be connected? With which prerequisites, interfaces, responsibilities, maintenance and support?
Verification and accountability
Who validates the configuration and the use case? What evidence is needed for the technical assessment and the other applicable checks?
Current status of these items: not documented on this site as capabilities already implemented. They must be completed before the project is approved and before any data are processed in the proposed environment.
What you need
to start well.
Use this list as a local reminder. It does not attest compliance or system readiness; your selections are not saved or sent.
0 of 6 items reviewed · A reminder, not a validation
The questions
that matter.
Can COGI already be installed on our systems?
This site does not attest that a complete installable package is available. The proposed configuration, the components available and those still to be developed must be documented by the technical team within the scope of the pilot.
Is our data sent to external models?
This site does not use models and does not send data to external services. For the real service, the answer depends on the chosen architecture: a data-flow map and documented conditions are needed for each supplier involved.
Does referring to the regulatory framework amount to compliance?
No. A general reference does not replace assessments of the actual use case, configuration, data and roles. The applicable checks must be carried out by the competent contacts.
Does “replaceable models” mean no dependencies?
No. It is an architectural approach that has to be translated into technical and operational conditions: compatibility, continuity, costs, timescales and preservation of information must be verified.
Is the PDF sheet a final technical document?
No. It is an editorial pre-assessment sheet, in Italian, with a matrix of the information to be completed. Version, date and limits are stated in the document.
It starts with a real questionA shared table.
A shared table.
Management and IT.
The first conversation is about jointly scoping the decision, data, technical conditions and verification criteria.
Start a conversation