KinaBot uses a source-available community model. This boundary keeps public benefit, community participation, commercial sustainability, and product claims separate and understandable.
The public repository is the transparent engineering and learning surface for:
- the maintained speech-sample feature engine and participant experience;
- scoring definitions, limitations, model-version behavior, and regression tests;
- privacy-aware and offline/private research patterns;
- public documentation, issue discussion, and reproducible learning cases;
- community contributions accepted under the contribution terms.
The aoi_kinabot_app/ product area remains authored and committed only by Aoi.
External issue reports, research, designs, testing, and patch proposals can
inform that application and must receive accurate credit, but Aoi independently
reviews and submits accepted product changes.
Availability in this repository does not grant commercial use beyond
LICENSE.md and does not establish clinical validation, institutional approval,
production fitness, or a support commitment.
AImoji may separately offer services or licensed capabilities such as:
- official AWS hosting and managed upgrades;
- organization administration, enterprise identity, and audit tooling;
- deployment, integration, migration, training, and support;
- operational monitoring, backup/restore, incident response, and service terms;
- customer-specific features or integrations developed under contract.
No item is promised until it is documented in a signed agreement. Commercial features must not weaken consent, deletion, privacy, security, accessibility, or responsible-use boundaries.
- Community contributors do not automatically endorse commercial offerings.
- A merged contribution does not make the contributor an AImoji employee, contractor, partner, or representative.
- A public feature is not automatically included in a supported commercial service.
- A commercial agreement does not convert KinaBot into a medical device or authorize diagnosis, surveillance, coercion, or high-impact decisions.
- Public issue discussion is not an appropriate place for confidential customer or participant information.
Material movement between community and commercial components should be documented with:
- the user and business rationale;
- ownership and license review;
- effects on contributors and existing users;
- privacy, security, accessibility, migration, and responsible-use analysis;
- version, release, deployment, and rollback implications.
The project should not remove a previously granted license from copies already received under that license. Future licensing changes must be prospective, versioned, and clearly announced.