Technology
Software as part of the scientific method.
When a result depends on code, the code is part of the method — and must meet the same rigour as any other research component: identified, documented, tested, verifiable.
The problem we avoid
Research software without provenance.
Much research software starts as a local script, grows without versioning and dies without documentation. When a result depends on that code, the science becomes irreproducible. Our answer is engineering discipline applied to real projects: versions, documentation, tests and traceability — from prototype to operation.
Engineering principles
How we build.
Traceability
Every datum has origin, version and context. From a cognitive response to a part request, everything is logged.
Modularity
Small, combinable, independently assessable components — from the cognitive platform to assisted-living modules.
Internationalisation
Architecture ready for multiple languages and contexts from day one.
Operation as a requirement
Software that cannot survive contact with real users fails the method. Operating is part of engineering.
Projects
Where the technology lives.
The Cognitive Assessment Platform is the priority technology-science project: digital cognitive assessment with time-based data and full traceability. Read the case →
In operating projects, technology serves operation: WooCommerce at PecasAuto.pt and Byblos Native, OJS at Scientia Humanae, WordPress at IDEG — each with its own R&D agenda.