Add BuildOrbitly v1 scaffold and deterministic pipeline

[bry92]

Motivation

• Implement a minimal, deterministic reference of BuildOrbitly v1 to enforce schema-bound software generation.
• Provide a typed compiler-style pipeline that binds intent to structure to prevent hallucinated architectures and plan overreach.
• Include a runnable example and documentation to bootstrap further development and iteration.

Description

• Add buildorbitly/ project scaffold with README.md, package.json, and .gitignore for run instructions and architecture docs.
• Add typed definitions in src/types.js and a src/schema-registry.js that defines static_surface, light_app, and full_product schemas.
• Implement core constrained services: services/intent-gate.js (compileIntent), services/schema-instantiator.js (instantiateSchema), services/planner.js (createPlan), services/scaffold-generator.js (generateScaffold), services/code-generator.js (generateCode), services/verify.js (verify), and services/acl.js (ACL).
• Wire the deterministic pipeline in src/pipeline.js and add src/main.js as a sample entrypoint that runs the pipeline and records ACL metrics.

Testing

• Ran npm run start --prefix buildorbitly to execute the full pipeline end-to-end as an automated smoke run.
• The run produced a static_surface intent, scaffolded artifacts, and returned verification.ok: true indicating no schema violations.
• No additional automated test suite was added in this change set.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1fd3b148bd

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Add the declared light_app entry file to schema files

verify() requires the scaffold to contain the schema entry, but this schema declares entry: 'index.html' while files only includes frontend/ and api/minimal.js; as a result, any request classified as light_app deterministically fails verification with Missing required entry point: index.html even when generation is otherwise correct.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Include full_product entry artifact in its schema file list

The full_product schema has the same mismatch: entry is server.js but files omits server.js, so runPipeline() for full-product intents always returns verification.ok: false due to a missing entry point, which blocks successful output for that entire task class.

Useful? React with 👍 / 👎.