Bound the assistant's role
The user assistant has no unrestricted tool access. Code controls context and output; instructions and filters bound responses. Product development and operations agents serve a different role.
Strahlkraft40+ / Digital product
A market opportunity turned into an AI product.
Strahlkraft40+ began with a market opportunity in women's wellbeing. We defined the product with its co-founder and built a platform with an AI assistant, content, payments and operational tools.
Product co-founded by Ionela Harosa and Ignacio Aredez
Live product · case documented as of October 2026
01 / The problem and its context
Strahlkraft40+
Ionela Harosa, Strahlkraft40+ co-founder, identified an opportunity in women's wellbeing. She understood the audience and had a business idea, without a technical background. We worked with her to define the experience, the assistant's scope, and how to offer content and paid access.
Who did what
Ionela contributed vision, content, brand and user support. Ignacio led technical definition, architecture, development, integrations and evaluation. Product definition and review were collaborative.
A view of what was built
The idea becomes an experience people can use
Portal, content and paid access connect with the assistant and its controls. Alongside the product, procedures and tools let the owner and team prepare content, review results and continue operations.
Explore this part of the product ↗
02 / Engineering decisions
Product, operations and engineering
Business vision + joint product definition
01User-facing product
- Portal and content
Access, reports and experience
- Assistant and memory
Context, continuity and boundaries
- Payments and access
Connected services
- Data protection
Consent, retention and deletion
02Operations tools
- Knowledge and creation
Study review, articles and images
- Channels and services
Newsletters, social channels and MCP
- Review and measurement
Team approval; events subject to consent
03Engineering and controls
- AI evaluation
Response, memory and model tests
- Change workflow
Assisted legal review and synchronisation
↺ Review feeds back into instructions, filters, skills and tests.
System decisions and boundaries
The user assistant and working agents have different roles. MCP connections belong to the working environment. Command-based legal review requires team supervision.
Design memory with rules
Define what information may be stored, with what consent and how it is deleted. Minimisation, retention and cascading deletion are accompanied by extraction and fact-continuity tests.
Evaluate model changes
Review responses, sensitive cases and memory quality when models change. Findings guide corrections to instructions, filters and tests.
Turn requirements into controls
Transparency, data protection and review of health claims for the intended use, GDPR, the AI Act and the German context. Decisions, risks and controls are documented.
Operations, automation and controls
How it works and is maintained
Sensitive information and memory
Consent, minimisation, retention criteria and cascading deletion. Tests examine memory extraction and continuity of facts.
Transparency and health claims
Information about AI interaction and boundaries, instructions, filters and contextual review of public claims.
Documented AI management
Scope, owners, risks, controls, providers and changes connected with evidence. Documentation references ISO/IEC 42001; it is distinct from a passed audit or accredited certification.
Skills and MCP connections
Reusable procedures for content, analysis and technical work; service integrations and a custom Meta Ads MCP server. The team has tools prepared through its iterations and corrections. Active connections depend on the working environment.
Content and study review
Procedures for newsletters, blogs and social channels with defined editorial voice and image styles. A scientific-paper auditing skill was also developed; it is in the disabled-skills archive, rather than running continuously. The product owner and team direct and review publication.
Measurement and consent
Usage, campaign and conversion events with consent controls and documented client/server flows. Measurement informs decisions and content revisions within the defined event scope.
Legal review by command
Within the commit workflow, the team invokes a command to review content against German rules and propose or apply corrections. This is supervised assisted review, not an automatic Git hook.
Automation and synchronisation
Purchase, access and communication workflows, scheduled tasks, and commands coordinating changes, documentation and working environments.
03 / How it is evaluated
How it is evaluated
Tests cover assistant behaviour and boundaries, memory quality and model migrations. Findings feed corrections that can be checked again. Management documentation connects scope, owners, risks and evidence; implementation continues to evolve and is not presented as accredited certification.
What was built
A live product with a portal, content, reports, an assistant with memory and payments. A working environment with agents, tools and reusable instructions supports operations and evolution. The product owner directs content and reviews what is published.
Live product · case documented as of October 2026
What we can bring to your project