Portfolio Notes
Refine draft wording before it appears in the public story.
The review queue keeps research notes and draft wording organized for future portfolio updates. Use it as an advanced editorial workspace.
Decision model
Copyable choices for future edits.
Buttons and packets copy context for a future update.
Project
Carcinus.org
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
FireAndStormRestoration.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Keep Angular wording tied to confirmed experience and current Angular/RxJS architecture context. Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
NeuralWikis.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
LocalEndpoint.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
NeuroWikis.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
AnarchyShelters.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
DarkMatterDrive.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
AIWikis.org
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
Calibrants.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
ErrorNotifier.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
Neurocumulus.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
LongTermSoftwareSolutions.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
Mechanotheist.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
2IX.org
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
IBSE.org
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
Neurokinetic.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
Symbiokinetic.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Project
Cogniverses.com
Suggested next step: Choose stronger wording, keep as background, or archive for traceability after review.
Research context: Public platforms and research surfaces are presented with professional context unless client delivery is part of reviewed evidence. Public summaries use high-level architecture language and protect confidential implementation details.
Capability
Python AI/data service boundaries
Suggested next step: Confirm wording before treating as an approved durable public claim.
Research context: Python examples communicate service-boundary patterns, validation, and AI/data workflow design.
Research brief workflow
These items help decide whether background research should become a curated Architecture Note.
review, narrow, then promote only approved implementation notes
Architecture note candidate: Architecture notes
review before using as durable UAIX specification language
Architecture note candidate: Architecture notes
keep as strategy candidate until domain direction is selected
Architecture note candidate: Architecture notes
leave retired until NeuralWikis/NeuroWikis live-site details are revalidated
Architecture note candidate: Architecture notes
safe to use as experience context; use reviewed wording for Modern Angular deployment context
Architecture note candidate: Architecture notes
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Possible Architecture Note draft.
Technical appendix
Structured packets support future maintenance passes and AI-assisted maintenance.
Decision packet only.
Decision packet only.
Decision packet only.
Decision packet only.
Decision packet only.
Decision packet only.
Decision packet only.
Decision packet only.
Decision packet only.
Decision packet only.
AI handoff guide
Guiding principles and safety anchors are ready for owner decision.
Mike said the values look good; use the decision page to copy an exact approval, edit, narrowing, replacement, or keep-as-draft decision packet.
Open AI handoff guide
Decision data
Open decision guideReviewer note
Draft workspace scope.
Portfolio Notes keep candidate wording, review packets, and follow-up decisions separate from polished public pages until the source and wording are confirmed.
Enterprise ValidatedFAQ
Common reviewer questions.
Visible page content matches the route-specific FAQ structured data.
What is the Review Desk?
It lists portfolio wording and project details that are useful but should be reviewed before stronger public positioning.
Does the queue publish private details?
It surfaces review state and professional contexts, portfolio-safe summaries rather than proprietary code or client-confidential information.