-
Notifications
You must be signed in to change notification settings - Fork 4
feat: integrate PDL governance core schema into PEW #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| node_modules | ||
| .next | ||
| yarn.lock | ||
| app/.next | ||
|
projectedanx marked this conversation as resolved.
|
||
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,14 @@ | ||
| # Non-Obvious Lessons & Governance Truths | ||
|
|
||
| ## Semantic Saponification and the Projection Tax | ||
| 1. **The Principle of "Semantic Saponification"**: Over long inference chains (e.g. 128k+ tokens), LLMs inevitably degrade rigid logic into homogenized, boilerplate "corporate" outputs. Without strict syntactic and semantic bounds (the "Negative Space Scaffolding"), an agent's reasoning slowly turns to soap. | ||
| 2. **The "Projection Tax"**: Forcing an LLM to generate rigid JSON/AST syntax while simultaneously ideating results in a 10-30% drop in reasoning accuracy. By bifurcating inference—generating high-entropy drafts first, then clamping them through a zero-entropy deterministic guard—we bypass this tax. | ||
|
|
||
| ## Topological Failure Mapping | ||
| 1. **The Betti-1 Loop**: When an agent gets caught in a cycle of writing, failing, reverting, and re-writing, it forms a "Betti-1 Loop" (a 1D topological hole in the latent manifold). These must be logged into a Symbolic Scar Archive to create a "repulsive virtual weight" mathematically repelling future iterations from the exact same failure. | ||
| 2. **Failure-Informed Prompt Inversion (FIPI)**: We do not log errors; we harvest them to inform continuous invariant boundaries. | ||
|
|
||
| ## Architecture and Governance | ||
| 1. **The Rule of Topological Layer Inversion**: Base deterministic layers (CI/CD, package management, schema definitions, and tests) MUST be compiled and established *first*. An architecture cannot be designed without physical bounds. | ||
| 2. **Paraconsistent Logic over Homogenization**: When faced with conflicting requirements, classical logic crashes. Using Paraconsistent Annotated Logic (PAL2v), the system holds conflicting truths simultaneously (using a semantic Golden Ratio of ϕ≈1.618 to the dominant frame and 1.000 to the subordinate) to maintain structural tension, avoiding the collapse of complex requirements into trivial compromises. | ||
| 3. **Stigmergic Concurrency**: Agents coordinate via "Epistemic Pheromones"—machine-readable file locks and AST semantic hypervisors to prevent logic shearing and collision during concurrent operations. |
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,6 @@ | ||
| /// <reference types="next" /> | ||
| /// <reference types="next/image-types/global" /> | ||
| /// <reference path="./.next/types/routes.d.ts" /> | ||
|
projectedanx marked this conversation as resolved.
|
||
|
|
||
| // NOTE: This file should not be edited | ||
| // see https://nextjs.org/docs/app/building-your-application/configuring/typescript for more information. | ||
| // see https://nextjs.org/docs/app/api-reference/config/typescript for more information. | ||
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
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.
Uh oh!
There was an error while loading. Please reload this page.