Open
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a formal specification document for the blueprint system at
docs/spec/BLUEPRINT.md. This is a documentation-only change — no code, no runtime impact.The spec defines a three-layer architecture for blueprints:
BlueprintTable,BlueprintField,BlueprintPolicy,BlueprintIndex) derived from DB introspectionAuthz*,Data*,Relation*,View*) driven by thenode-type-registrypackage and its JSON Schema definitionsBlueprintExtensionentries for frontend scaffolding, deployment recipes, agent skills, etc.Also documents the type generation pipeline (
generate-types.ts), validation rules, versioning policy, and a complete CRM example blueprint.Review & Testing Checklist for Human
BlueprintExtensiontype withnamespace/kind/version/configdoes not exist in the codebase yet. Verify you're comfortable with the spec documenting this as a design alongside the already-implemented Layers 1 and 2. Consider whether it should be marked more clearly as "proposed" or "future."BlueprintPolicydiscriminant field name. The spec and examples use$typefor the policy type field. The introspection-derived version usespolicy_type(the actual DB column name). Confirm which is canonical and whether the spec/examples are consistent with whatconstruct_blueprint()actually accepts.RelationBelongsToparams (field_name,nullable) andDataSearch.full_text_search.source_fieldsshape.Notes
docs/spec/SLICING.md(cross-referenced in the doc).Link to Devin session: https://app.devin.ai/sessions/ce1b2dafd42341bea5d7793b0c05ba6c
Requested by: @pyramation