CloudWinks · Foundation apps

CoderCodyTechnical brief

CoderCody organizes the prompts used to guide development and the outputs those prompts produce. It keeps a traceable path from a prompt to its documents, plans and extracted records, so work on an application can be followed later.

Read the business brief · PDF

1. Architecture in brief

CoderCody is a Foundation app with platform tenancy. It holds prompt categories, prompts, target applications, output documents, and structured extracts such as implementation phases and tasks, research findings, seeding data and database definitions. CloudWinks supplies the application runtime and Crux the shared identity. The product model is a traceable register, not an agent runtime.

2. Service boundary and intake

Prompts are organized in categories and stored as templates with versions and metadata. An output document is recorded against a prompt and a target application. Structured records can then be extracted from that document into the appropriate tables. Ordinary create, update and review operations use the shared platform services.

3. Data handled

The model stores prompt categories and prompts, system applications, output documents, and extracted records including phases, tasks, research findings, seeding data, database definitions, opportunity and gap analyses, and related status notes. CoderCody owns the prompt, the output and those extracts. It does not own the running application that was described, the agent that may later use a prompt, or the message that may carry a document.

4. Integrations and ownership

CloudWinks and Crux provide the runtime and identity. A prompt or output can name the application it concerns. Database definitions in an output may later inform application records. WorkerBee remains the agent service; CoderCody does not run agents. Murphy can receive storage or review problems. CoderCody owns the traceable register, not those other services.

5. Security and access

Access follows platform grants and the CloudWinks tenancy of this app. A visible prompt is not a grant to change every output or to open every target application. Prompt and output records stay inside the platform boundary. Identity and access remain with Crux and KeyKook.

Competitive context

AlternativeIts focusCloudWinks product focus
LangSmithVersioned prompts and traces of model inputs and outputs.Prompts and outputs tied to CloudWinks application work, including plans and extracted records.
PromptLayerPrompt versioning and logs that link each run to a prompt version.A shared register of development prompts and their documents, not only model-call logs.

Read the business brief →

← More Foundation apps apps · All application briefs · How the framework works