Compatibility entrypoint for legacy requests explicitly naming oro-ologbon.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
Compatibility entrypoint only.
oro-fun-sigidi.oro-fun-eniyan.Do not maintain a third writing method here.
quantipixelsBuild and verify an accepted coding change or fix. Use directly when the outcome is sufficiently clear, or within an atona initiative; exclude initiative coordination, standalone planning, review, and publication.
quantipixelsGuide requested work through completion using relevant installed skills and conditional routes. Use as the operating entrypoint for skill-driven work, to choose the next owner, resume work, resolve adjacent ownership, or request the installed skill inventory.
quantipixelsEstablish, sharpen, or reconcile one project's canonical domain model and its durable records. Use when project-specific terms, conceptual identities, domain/context boundaries, relationships, ownership, invariants, .learnings, .nongoals, or ADRs need to be defined, changed, or maintained.
quantipixelsDesign, survey, or review the technical structure of a software system or consequential module at the smallest scale needed to resolve the architecture question. Use for architectural friction, system boundaries, module/interface/seam shape, data/state ownership, integrations, deployment, quality scenarios, trade-offs, migration/recovery, or architecture sufficiency; exclude initiative lifecycle planning, user-decision closure, implementation, workspace infrastructure, and code-review verdicts.