sdcorejs-nestjs

SDCoreJS NestJS Executor

Shared protocols

Before execution:

1. Read _refs/shared/runtime-protocols.md, then apply _refs/shared/tasklist.md.
2. Read and apply _refs/shared/project-context.md as a read-only, relevance-first context assembler.
3. Read _refs/shared/artifact-lifecycle.md and merge producer artifact_context through the finishing tail.
4. Read and apply _refs/shared/user-choice-prompt.md before any user-facing choice, approval, or finish gate.
5. Use valid summary sections when available. Missing or stale summary never blocks generation; continue with targeted reads or a scoped code map.
6. Read _refs/nestjs/pack-manifest.json, _refs/nestjs/profile-contract.json, and _refs/nestjs/core-catalog.md.
7. Before authoring a helper, read _refs/shared/sdcorejs-utils.md.

Resolve the generation contract once

Resolve profile exactly once from the approved plan or fresh project summary. Use simple only when no profile is declared. Validate the resolved profile against profile-contract.json, store it in the run context, and pass the same resolved profile unchanged to every dispatched pack. A pack must not infer, override, or downgrade the profile.

Fail before writing when:

• the manifest/profile schema is invalid;
• required pack inputs are missing;
• an output would escape the target root or overwrite undeclared files;
• an enterprise operation lacks trusted tenant context;
• authentication or permission metadata cannot be generated.

Dispatch graph

Read packs on demand in manifest dependency order:

1. _refs/nestjs/write-code/init-project.md for a new backend.
2. _refs/nestjs/write-code/init-admin.md for the required authn/authz authority.
3. _refs/nestjs/write-code/init-module.md for each bounded context.
4. _refs/nestjs/write-code/init-entity.md for explicit entity routes and stacks.
5. _refs/nestjs/write-code/actions.md for workflow, import, export, or custom actions.