Repository navigation
FAQ
No. Arketype is a non-normative library of candidate structures and empty workspace templates. It reuses the bundled Authoring Kit and makes no new Framework-level contract.
Yes. A semantic reference may support teaching, research, museums or personal study. A casefile may support many properly governed forms of follow-up. Profiles capture the situation; archetypes capture the fundamental structure.
No. Each has a dominant reading motif and may also have secondary patterns. A knowledge graph can be rendered as a tree for one task, but the diagram must not silently discard native relationships.
No. Recipe links remain unresolved design proposals. Owners, exact references, contracts and any permitted semantic transfer have to be specified separately.
No. It checks local technical structure. A recorded testimony must remain an attributed report unless separately evaluated; a diagnostic hypothesis is not a confirmed cause.
No. It is an offline generated projection. Run python arketype.py build-html after changing JSON inventories.
No. The wiki/ directory is ready-to-publish Markdown; GitHub Wikis are separate repositories. Follow Publishing the Wiki.
In the UI assets and presentations. The Markdown README intentionally has no embedded logo.
Do not put private records in the public library templates. A production workflow must first implement access restrictions, lawful collection basis where relevant, retention, audit, identity controls and appropriate governance.
Arketype Wiki
- Home
- Getting Started
- Desktop Launcher
- Developer Ops
- Ecosystem Compatibility
- Architecture
- Visual Grammar
- Archetype Catalog
- Use-Case Profiles
- Composition Recipes
- Working with Templates
- CLI Reference
- Data Formats
- Validation and Testing
- Security and Boundaries
- Extending Arketype
- Publishing the Wiki
- Glossary
- FAQ