A working call to confirm the Alpha scope, controlled release model, legal priorities and the communication system needed before the next presentation.
The MVP remains centered on voice, text, memories and personal stories. Biometrics move later, while compliance, a controlled user cohort and an emotionally clear public narrative become immediate priorities.
Product alignment call.
Remote working session.
The source recap has been normalized into confirmed product, governance, communication and delivery decisions.
The first usable Saelia release will focus on voice recordings, text, memories, personal stories and user-generated content. Biometric data is intentionally postponed to reduce implementation complexity and avoid introducing sensitive interpretation before the core product loop is stable.
The MVP should open first to a small, selected cohort. Consent, privacy documentation, AI transparency, data handling and the August 2026 AI Act milestone must evolve with the platform. A limited release makes feedback, governance and legal review more manageable.
Saelia will initially orchestrate external AI services rather than train a proprietary model. The architecture should preserve the option to bring more intelligence in-house later, after the product has data, validated use cases and a clearer technical moat.
The dashboard is no longer just an internal demonstration surface. It must clearly communicate the recording, session, data collection and processing workflow. Security and Phoenix are still missing, while labels, examples and navigation need another usability pass before the next presentation.
The first useful outcome is a living, organized album of memories, emotions, experiences and family knowledge. Saelia should demonstrate value before its long-term continuity vision is available, giving users a clear reason to keep recording and returning.
Dominika will become Saelia's public presenter and recognizable voice. Her role is to explain the philosophy, emotional value and human relevance of the project, while technical demonstrations remain a separate and complementary part of presentations.
The communication system should begin with roughly 50 foundational questions and about five hours of natural recorded answers. That source material can become interviews, podcasts, long-form videos, short social clips, conference material and presentation segments.
Public communication should emphasize continuity, preservation, identity, evolution and hope. Saelia should tell stories about meaning and family knowledge rather than lead with technical features or explicit post-mortem language.
The 24 July checkpoint targets an Alpha that is approximately 90% complete, with a working dashboard, polished live presentation and conference-ready material. Company formation remains targeted for late August or early September in Poland.
The call was organized around product, legal and marketing. Its purpose was to confirm the MVP roadmap, review the dashboard and development status, and define how Saelia should be communicated before the conference and company foundation. The discussion marked a shift from building isolated software functions to coordinating product, trust and public meaning.
The current development direction remains valid. The Alpha should collect voice recordings, text, memories, stories and other user-generated material. It should not attempt to solve biometrics, custom hardware or every future identity feature. Delaying biometrics lowers implementation risk and keeps claims closer to what the product can currently prove.
GDPR, consent, data storage, AI transparency and the August 2026 AI Act milestone were identified as active product constraints. Policies, consent states and data procedures must develop alongside the interface. The preferred release model is a controlled cohort of selected users, which allows direct feedback and keeps compliance work proportionate during the Alpha.
Saelia will initially combine external AI providers instead of operating its own model. This gives the team access to mature capabilities without delaying the MVP. The long-term architecture should still support more proprietary intelligence, but that investment becomes meaningful only after Saelia has accumulated permissioned data, repeatable workflows and evidence of differentiated value.
The live demonstration moved to Microsoft Teams after screen-sharing issues. The session confirmed that Dominika needs continuous visibility into dashboard navigation, sessions, data collection and the complete user workflow so she can explain the product accurately. After each meeting, links, decks and development materials should be shared with the full team.
The dashboard is becoming one of Saelia's core product surfaces. It needs clearer labels, actions and examples that create an immediate emotional connection. Recognizable locations such as Barcelona or Valencia were preferred over less universal examples. Security and Phoenix were identified as missing sections to address before the next major presentation.
The three meeting participants should be among the first controlled users, allowing the team to experience Saelia from the user side before a broader release. Personality and consciousness assessments may later support the experience, but categories and color systems must be simplified so ordinary users can understand them without specialist explanation.
The team asked what a paying user should receive after only two weeks. The clearest answer was an organized, living album of memories, emotions, personal experiences and family knowledge. This gives Saelia useful present-day value while creating a longitudinal archive that may become more meaningful over time and across generations.
Dominika accepted the role of public narrator and recognizable face of Saelia. Her communication should focus on philosophy, vision and emotional relevance rather than technical architecture. This creates a clearer division between the human story and the software demonstration while keeping both parts coordinated.
The team prefers educational content over conventional advertising. A working format is a bank of approximately 50 questions covering digital identity, memories, emotion, Time Bubble, consciousness and the reason Saelia exists. Around five hours of recorded answers can be edited into podcasts, interviews, YouTube episodes, Instagram reels, TikToks, conference material and presentation clips.
The communication should be emotional, authentic, human and empathetic. It should lead with meaning rather than features, and show why preserving thoughts, emotions, feelings and identity matters beyond storing photos or files. Terms centered on death should be replaced with continuity, preservation, evolution, digital existence and hope.
The broader mission remains enabling continued interaction with the memories, voice, stories and knowledge of people we care about. Future demonstrations may include conversations with reconstructed personalities based on preserved data, but this remains a long-term direction rather than a promise of the Alpha release.
The proposed format separates a concise technical platform explanation from a longer philosophical narrative led by Dominika, supported by live demonstrations. This structure should let audiences understand the emotional reason for Saelia and then see enough working product to trust that the vision has an executable foundation.
Company formation remains planned for late August or early September in Poland. Dominika will coordinate with the selected notary after receiving the contact details. Before that, the 24 July meeting is the next checkpoint: approximately 90% of the Alpha, a working dashboard, a polished live presentation, conference-ready material and stronger overall product maturity.
Concrete work extracted from the call, separated from long-term product vision.
Bring the Alpha to approximately 90% completion, with a working dashboard, polished live presentation, conference-ready material and a stable voice, text and memory workflow.
Add or resolve Security and Phoenix, improve labels and actions, and replace weak examples with recognizable, emotionally immediate content.
Advance privacy policies, explicit consent, AI transparency and data procedures in parallel with the Alpha, using a selected-user release instead of an immediate public opening.
Draft approximately 50 foundational questions and plan roughly five hours of recorded answers with Dominika for long-form and short-form channels.
Create a practical messaging guide centered on preservation, identity, evolution and hope, with clear terms to avoid in public communication.
Distribute pipeline links, presentations and current development material to all team members so the public narrative always matches the actual product state.
Start with Simone Pagani, Simone Asperti and Dominika Marciniak as initial users before inviting a broader but still limited testing group.
Keep late August or early September as the company formation target. Share the notary contact details so Dominika can coordinate the local process.