Katteke prefers open standards, documented interfaces, exportability, and source availability where publication is safe and strategically appropriate. Open source is a deliberate product and repository decision, not permission to publish every private workspace.
Repository decisions
Before opening a repository, decide and record:
- product purpose and expected users;
- code, documentation, asset, and trademark boundaries;
- license compatibility for dependencies and copied material;
- secret, personal-data, customer-data, private-path, and machine-state scans;
- maintenance, security reporting, contribution, release, and support expectations;
- whether private operational or commercial material must be split out first.
No repository becomes public merely because another Katteke project is public.
Intended licensing direction for this portal
Katteke intends to consider CC BY 4.0 for original public prose and Apache-2.0 for original public machine-readable specifications, schemas, and code examples. These are not current licenses.
Both choices require a recorded licensing and legal review, explicit approval by Rei, an effective date, and updated license files before any grant exists. Until then, original portal content is all rights reserved. Third-party work keeps its own terms; Katteke trademarks and excluded material are not relicensed.
See licensing status for the controlling notice. Product repositories may choose different licenses through their own reviewed and accepted decision.
Business model
Avoid technical lock-in as the moat. Sustainable value should come from accountable builds, signed releases, support, migration, integration, compliance work, training, and managed operation—not from trapping customer data or hiding essential interfaces.