- JavaScript 89.6%
- TypeScript 5.6%
- CSS 2.1%
- Makefile 1.6%
- HTML 1.1%
kilo
417372f189
All checks were successful
Development Checks / check (push) Successful in 16s
Owner-authorized repository-local review policy correction. Exact HEAD |
||
|---|---|---|
| .forgejo/workflows | ||
| .kilo | ||
| docs | ||
| scripts | ||
| src | ||
| tests | ||
| .gitignore | ||
| .markdownlint-cli2.jsonc | ||
| .node-version | ||
| .npmrc | ||
| .prettierrc.json | ||
| .secretlintrc.json | ||
| AGENTS.md | ||
| CONTRIBUTING.md | ||
| index.html | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| tsconfig.json | ||
| vite.config.ts | ||
Creatidy Console
Public, local-first operator interface for Creatidy. The intended experience answers: What is working? Why did the system make these decisions? Does it need anything from me?
Forgejo is canonical for source, issues and review: https://forgejo.creatidy.com/Creatidy/creatidy-console. GitHub is a one-way public mirror, not a second development workflow.
Current Status
Repository foundation only: English product/architecture context, registered integration backlog, development tooling and a non-operational web scaffold. There are no producer connections, live task views, product commands, notifications or product installation guarantees. The scaffold does not simulate healthy resources.
Console presents producer-owned facts and delivers authorized commands to their owners. It is not a scheduler, harness, inference gateway, model catalog, shared database or replacement for Router administration or Forgejo.
Development
Use the declared Node/npm versions, then make help, make install and
make check. make dev serves only the scaffold on loopback. make build
produces a local static artifact, not a production deployment. See
contribution guidance for exact commands and evidence limits.
develop is the integration/default branch. Normal work uses one selected
issue, one focused branch and one independently reviewed PR into develop.
Repository-local commands: /implement-issue, /review-pr, /finish-pr and
/loop. Standalone implementation requires owner issue selection; review is
read-only; finish remediates but never merges. Only an explicit owner /loop
invocation authorizes deterministic canonical issue selection and exact-approved
Forgejo PR integration into develop, verified acceptance/issue closure, then
selection again. It uses one primary implementation checkout and a persistent
excluded review ledger, with bounded temporary isolation/technical remediation
before owner escalation, not a second controller or Scarcity Router operation.
Main, promotion, release and deployment remain outside this authority. See
contribution guidance and agent entry point.
Authoritative Context
- Documentation index: one home per topic.
- Product and boundaries: mission, scope and decisions.
- UX and states: journeys and low-fidelity interaction descriptions.
- Contracts and evidence: verified producer behavior and gaps.
- Security and privacy: threat model and authority boundaries.
- Technology and reuse: initial toolchain and alternatives.
- Roadmap and traceability: actual issues, G01-G13 and gates.
- Agent guidance: concise development instructions.
Bootstrap issue #1 holds delivery/review evidence. GitHub issues are disabled to avoid a parallel backlog. Source guidance is host-neutral; canonical issue and PR creation remain usable.
Workflow migration #16 records the owner-authorized development command migration, not Console runtime or producer integration functionality.
Licensed under Apache-2.0. See LICENSE, NOTICE and the reuse record. No proprietary DemandTrace code/assets are copied.