adminprojects/eddie-soehnel-portable-identity-document-OPEN
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
6cbdb6d23f
eddie-soehnel-portable-iden.../review-drafts/PID-what-i-have-projects-review-2026-06-16.md
eddiesoehnel 6cbdb6d23f added
2026-06-16 12:38:11 -06:00

22 KiB
Raw Blame History

PID What I Have Review Draft

Agent response to human when this review draft is complete: This is a draft for your review before anything is added to your Portable Identity Document (PID).

Please edit freely:

  • delete anything that should not be included
  • correct anything inaccurate
  • add missing context, links, examples, names, or proof
  • mark private items that should be removed or generalized
  • strengthen anything that feels too vague or too narrow

After you edit this draft, ask the agent to continue from your revised file and update the WHAT I HAVE section of your PID.

Run Scope

  • Review date: June 16, 2026.
  • Approved source reviewed: C:\projects.
  • PID source reviewed: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\Eddie-Soehnel-Portable-Identity-Document-Level-1.md.
  • Prior draft format referenced: C:\projects\ES\eddie-soehnel-portable-identity-document-OPEN\PID-update-review-draft-2026-06-16.md.
  • Review goal: identify durable assets, scripts, processes, workflows, and project systems under C:\projects that could be added to or made more explicit in the PID WHAT I HAVE section.
  • Privacy posture used: standard privacy. I avoided private hostnames, IP addresses, credentials, raw customer/subscriber data, private operational topology, and personal/family/health specifics. Some items are marked Review where a public PID should generalize details.
  • PID update status: awaiting user review. Nothing has been appended to the PID.

METADATA, ONTOLOGY AND CONTEXT / WHAT I HAVE

Proposed Addition

  • [Fact] A Git-backed personal operating system rooted in C:\projects, with project repositories, source-controlled Markdown, task workflow logs, publication receipts, skill files, infrastructure inventories, and Google Drive/JSON/NAS/email sources treated as inputs for AI-assisted recall and updates.
    • Evidence: C:\projects\1-flows\flows\daily-log.md; C:\projects\1-flows\flows\Infra.md.
    • Confidence: High.
    • Privacy: Review. Public wording should describe the operating model without listing sensitive data sources in too much detail.

Proposed Addition

  • [Fact] A daily operating and memory-capture workflow that connects task planning, audio logs, project changelogs, CRM/JSON records, calendar review, Git updates, media processing, backups, and AI-assisted prompts into one recurring review loop.
    • Evidence: C:\projects\1-flows\flows\daily-log.md.
    • Confidence: High.
    • Privacy: Review. Keep specific personal, family, health, and sensitive operational details out of the public PID.

Proposed Addition

  • [Fact] An infrastructure review flow for keeping edge compute, hardware, software, VMs, domains/routing, cron jobs, backups, telemetry, and project references synchronized as work changes.
    • Evidence: C:\projects\1-flows\flows\Infra.md.
    • Confidence: High.
    • Privacy: Review. Mention the capability, not private routing details.

Proposed Addition

  • [Fact] A reusable spec-driven product development operating system for building software, services, physical products, workflows, and agents from structured Markdown specs, tasks, srv/ execution code, data-ops/, tests, decisions, personas, and system ontology.
    • Evidence: C:\projects\productivity\product-dev-os-OPEN\README.md; C:\projects\productivity\product-dev-os-OPEN\specs\3_product_development_s\system-ontology-framework\system-ontology-framework.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A concrete AI-native knowledge-structuring architecture that separates human-readable Markdown/HTML from AI-readable chunks, Q&A, CIS/chunk-intelligence signatures, control-plane metadata, discovery files, versioning, policy overlays, and future vector/graph enrichment.
    • Evidence: C:\projects\productivity\ai-knowledge-structure-OPEN\README.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A structured website builder that converts Markdown content into a fast, static, AI-readable website with Hugo, semantic chunks, Q&A JSON, JSON-LD, ai-index.json, llms.txt, agents.md, skills.md, sitemap, robots, and .well-known discovery/security files.
    • Evidence: C:\projects\productivity\structured-website-builder-OPEN\README.md; C:\projects\publication-receipts-to-open\2026-06-09-structured-website-builder-publication-receipt.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] Deterministic website-publishing scripts that sync authored content to Hugo, build AI discovery indexes, generate root discovery files, and publish Hugo output while preserving key machine-readable files.
    • Evidence: C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\sync_content_to_hugo.py; C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\build_ai_index.py; C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\build_discovery_files.py; C:\projects\productivity\structured-website-builder-OPEN\skills-scripts\publish_hugo_output.py.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A website content-structuring skill stack for authoring, chunking, semantic Q&A generation, AI index/discovery materialization, HTML semantic artifact checks, contact-form deployment, and conversion of the builder to new website projects.
    • Evidence: C:\projects\indx\indx-front-website\skills-scripts\author-content-structuring-skill.md; C:\projects\indx\indx-front-website\skills-scripts\cis-guided-semantic-chunk-generation-skill.md; C:\projects\indx\indx-front-website\skills-scripts\semantic-qa-materialization-skill.md; C:\projects\indx\indx-front-website\skills-scripts\html-semantic-artifacts-checker-skill.md; C:\projects\indx\indx-front-website\skills-scripts\discovery-files-materialization-skill.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A master SEO/GEO/findability framework for the AI era covering differentiation, trust/authority, digitization, semantic structuring, traditional search submissions, industry ontologies, knowledge graphs, and agentic search optimization.
    • Evidence: C:\projects\productivity\seo-geo-OPEN\README.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A repeatable private-to-public publication workflow for sanitizing operational repos into useful public templates, including explicit source/file gates, anonymization maps, leak scans, validation tiers, ratchet artifacts, and publication receipts.
    • Evidence: C:\projects\productivity\misc-productivity-tools-OPEN\skill-repo-publication-workflow.md; C:\projects\publication-receipts-to-open\2026-06-09-structured-website-builder-publication-receipt.md; C:\projects\publication-receipts-to-open\2026-06-11-email-campaigns-prod-app-publication-receipt.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A publication-receipt library documenting sanitized releases and review gates for open-source/project-template work, including structured website builder, edge data center, Postmark/Listmonk operations, and email-campaign tooling.
    • Evidence: C:\projects\publication-receipts-to-open.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A multi-brand email campaign operations system using Listmonk and Postmark for LOD, EddieSoehnel.com, and iNDX, including HTML campaigns, welcome emails, open/click tracking, non-open follow-ups, exports, backups, and future segmentation/automation planning.
    • Evidence: C:\projects\productivity\email-campaigns-prod-app-OPEN\README.md; C:\projects\productivity\email-campaigns-prod-app\tasks-workflows.
    • Confidence: High.
    • Privacy: Review. Avoid private list sizes, recipients, endpoints, and operational credentials.

Proposed Addition

  • [Fact] Email intelligence scripts for exporting Listmonk data, pulling Postmark telemetry, backing up Listmonk, sending welcome emails, and analyzing LOD/iNDX non-open segments for follow-up campaigns.
    • Evidence: C:\projects\productivity\email-campaigns-prod-app\srv\export_lod_listmonk_data.sh; C:\projects\productivity\email-campaigns-prod-app\srv\export_indx_listmonk_data.sh; C:\projects\productivity\email-campaigns-prod-app\srv\pull_lod_postmark_telemetry_from_workstation.sh; C:\projects\productivity\email-campaigns-prod-app\srv\pull_indx_postmark_telemetry_from_workstation.sh; C:\projects\productivity\email-campaigns-prod-app\srv\analyze_lod_nonopens.py; C:\projects\productivity\email-campaigns-prod-app\srv\analyze_indx_nonopens.py; C:\projects\productivity\email-campaigns-prod-app\srv\send_welcome.py; C:\projects\productivity\email-campaigns-prod-app\srv\backup-listmonk.sh.
    • Confidence: High.
    • Privacy: Review. Public PID can name the workflow but not private infrastructure values.

Proposed Addition

  • [Fact] A local-first edge data center documentation stack covering hardware tiers, VM strategy, networking, security practices, backup/disaster recovery, monitoring, power resilience, and solar-supported infrastructure.
    • Evidence: C:\projects\infra\edge-data-center-main-OPEN\README.md; C:\projects\infra\edge-data-center-main\README.md; C:\projects\infra\edge-data-center-main-OPEN\PUBLICATION_WORKFLOW.md.
    • Confidence: High.
    • Privacy: Review. Keep public wording at architecture/capability level.

Proposed Addition

  • [Fact] A structured hardware and software inventory for the edge environment, with repos for machines, routers, UPS/power systems, NAS devices, Proxmox/Ubuntu VM software, Caddy routing, Gitea, ops monitoring, email campaign VM, and fleet/software inventory scans.
    • Evidence: C:\projects\infra\hardware; C:\projects\infra\software; C:\projects\infra\software\ops-monitor\README.md; C:\projects\infra\software\vm-software-inventory-scan\README.md; C:\projects\infra\software\caddy-router\README.md; C:\projects\infra\software\gitea-prod-app\README.md.
    • Confidence: High.
    • Privacy: Review. Generalize names, topology, and endpoints in public PID.

Proposed Addition

  • [Fact] A leak-scan/security-publication process for public infrastructure templates, including PowerShell leak-scan scripts, sanitization maps, .gitignore guardrails, and human-review gates before public publication.
    • Evidence: C:\projects\infra\edge-data-center-main-OPEN\scripts\leak-scan.ps1; C:\projects\infra\edge-data-center-main-OPEN\sanitization-map.md; C:\projects\infra\edge-data-center-main-OPEN\PUBLICATION_WORKFLOW.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A PID template and PID maintenance skill system, including initial-creation and update-maintenance skills, source-authorization rules, review drafts, run receipts, and a maturity model for evolving PIDs into stronger AI-readable identity layers.
    • Evidence: C:\projects\indx\portable-identity-document-template-OPEN\README.md; C:\projects\indx\portable-identity-document-template-OPEN\PID-template.md; C:\projects\indx\portable-identity-document-template-OPEN\PID-maturity-model-roadmap.md; C:\projects\indx\portable-identity-document-template-OPEN\skills\PID-initial-creation-skill.md; C:\projects\indx\portable-identity-document-template-OPEN\skills\PID-update-maintenance-skill.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A working NetworkSIG/PaddleNet business and system strategy for using Portable Identity Documents as structured inputs for matching, trust, freshness, permissions, telemetry, local-agent processing, and future agent-to-agent networking.
    • Evidence: C:\projects\paddlenet\paddlenet-business\specs\1_strategy_s\nsig-vision-strategy.md; C:\projects\paddlenet\paddlenet-app\paddlenet-nsig\paddlenet-nsig-pid-ingestion.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A PaddleNet telemetry-learning concept where agents report anonymized session/match telemetry so the network can learn which PID sections, metadata fields, trust signals, match categories, and human feedback patterns create real value.
    • Evidence: C:\projects\paddlenet\paddlenet-app\paddlenet-nsig\paddlenet-nsig-pid-ingestion\3_product_development_s\gate access by requiring telemetry upload.md.
    • Confidence: High.
    • Privacy: Review. Public PID should describe the anonymized learning loop, not any live user data.

Proposed Addition

  • [Fact] A PaddleNet/iNDX front-website publishing implementation that uses the structured website builder pattern for content, semantic artifacts, discovery files, contact forms, production launch notes, and ongoing task workflows.
    • Evidence: C:\projects\paddlenet\paddlenet-app\paddlenet-front-website\README.md; C:\projects\paddlenet\paddlenet-app\paddlenet-front-website\UPDATES.md; C:\projects\paddlenet\paddlenet-app\paddlenet-front-website\tasks-workflows; C:\projects\indx\indx-front-website\tasks-workflows.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A PTC/COLAB innovation sprint project space for converting outdoor/association problems into structured challenge work, student/technologist collaboration, and AI-era innovation programming.
    • Evidence: C:\projects\paddlenet\paddlenet-colabSIG\ptc-colab-2026-innovation-sprint\README.md; C:\projects\future-map\future-map\sales\2026-06-SIA-proposal.md.
    • Confidence: Medium.
    • Privacy: Review. Some proposal/outreach material may be pre-public.

Proposed Addition

  • [Fact] A Future Map research workspace for AI, job unbundling, business ownership, public lands, geopolitics, social contracts, consumer behavior, infrastructure sovereignty, and emerging business-model shifts.
    • Evidence: C:\projects\future-map\future-map\notes.md.
    • Confidence: High.
    • Privacy: Safe if summarized at theme level.

Proposed Addition

  • [Fact] A Light of Dog AI operations/process layer, including a private-training-during-boarding workflow that uses portable recording, speech-to-text, AI summarization, and linked content to produce richer boarding logs/client reports.
    • Evidence: C:\projects\LOD\lod-private-training-during-boarding-stay\README.md; C:\projects\LOD\lod-ai-os.
    • Confidence: High.
    • Privacy: Review. Avoid client/dog-specific details in public PID.

Proposed Addition

  • [Fact] LOD operational scripts and app maintenance utilities, including payment counter reseeding, file path migration, customer data repair, API app work, and AI OS/spec structure.
    • Evidence: C:\projects\LOD\lod-api\scripts\reseed_payment_counter.py; C:\projects\LOD\lod-api\scripts\reseed_all_counters.py; C:\projects\LOD\lod-api\scripts\migrate_file_paths.py; C:\projects\LOD\lod-api\scripts\fix_all_customers.py; C:\projects\LOD\lod-ai-os\specs.
    • Confidence: High.
    • Privacy: Review. Keep private app internals generalized.

Proposed Addition

  • [Fact] A miscellaneous skill and productivity tool library with reusable prompt/workflow skills for publication, product analysis, brainstorming, bias avoidance, autonomous large-build management, database search beyond Google, Google Docs Markdown conversion with images, Garmin FIT extraction, and Git/Gitea release processes.
    • Evidence: C:\projects\productivity\misc-productivity-tools-OPEN.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A ratchet-based skill framework and skill-template repo for turning recurring agent mistakes, workflow lessons, validation gaps, and review patterns into durable skill instructions, checklists, fixtures, and anti-patterns.
    • Evidence: C:\projects\productivity\misc-productivity-tools-OPEN\skill-template\ratchet-based-skill-framework.md; C:\projects\productivity\misc-productivity-tools-OPEN\skill-template\README.md.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A Google Docs Markdown conversion workflow with image extraction support, useful for moving cloud-authored long-form documents into Git/Markdown workflows while preserving media.
    • Evidence: C:\projects\productivity\misc-productivity-tools-OPEN\google-doc-md-conversion-with-images\google-doc-md-conversion-skill.md; C:\projects\productivity\misc-productivity-tools-OPEN\google-doc-md-conversion-with-images\extract_md_images.py.
    • Confidence: High.
    • Privacy: Safe.

Proposed Addition

  • [Fact] A small external-platform-post publishing process that exports tagged JSON hub records into Word/document output for website publication.
    • Evidence: C:\projects\productivity\external-platforms-posts-publish\README.md; C:\projects\productivity\external-platforms-posts-publish\srv\auto_fix_json_and_export_external_posts.py.
    • Confidence: High.
    • Privacy: Review. Public PID should describe the process without private file paths or unpublished content details.

Proposed Addition

  • [Fact] A CRM/contact-list utility repo with scripts for finding and working with contact data.
    • Evidence: C:\projects\productivity\crm-contacts-list\README.md; C:\projects\productivity\crm-contacts-list\srv\find.py.
    • Confidence: Medium.
    • Privacy: Review. Do not expose private contacts or CRM contents.

Proposed Addition

  • [Fact] A Google Analytics workspace and analytics-oriented project area for measuring web traffic and campaign performance.
    • Evidence: C:\projects\productivity\google-analytics\README.md.
    • Confidence: Medium.
    • Privacy: Safe if generalized.

Proposed Addition

  • [Fact] Local working copies of advanced agent/memory/reference stacks, including GBrain, GStack, and OpenProse, used as research material for agent memory, skill ecosystems, AI-assisted development roles, responsibility runtimes, and Markdown contracts for agent execution.
    • Evidence: C:\projects\repos\gbrain\README.md; C:\projects\repos\gstack\README.md; C:\projects\repos\prose\README.md.
    • Confidence: High that the working copies exist; Medium on how strongly to claim ownership.
    • Privacy: Safe if phrased as "local reference/evaluation repos" rather than owned inventions.

Proposed Addition

  • [Inference] A practical advantage worth making explicit: you do not only have ideas about AI-native systems; you have a working pattern of turning them into repos, skills, deterministic scripts, public templates, private ops docs, receipts, and repeatable workflows.
    • Evidence: Cross-cutting pattern across C:\projects\productivity, C:\projects\indx, C:\projects\infra, C:\projects\paddlenet, C:\projects\publication-receipts-to-open, and C:\projects\1-flows.
    • Confidence: High.
    • Privacy: Safe.

POSSIBLE GROUPING / MERGE NOTES

  • The existing PID already says you have "many more projects, skills, workflows, tools and processes." This review suggests replacing or expanding that broad line with specific groups:

    • AI-readable identity and PID systems
    • AI-era findability and structured website publishing
    • product-development OS and system ontology frameworks
    • local-first edge infrastructure and ops inventory
    • email/list/telemetry automation
    • private-to-public publication and sanitization workflows
    • daily operating system and memory-capture flows
    • LOD, PaddleNet/iNDX, Future Map, and PTC/SIA applied project spaces
    • reusable skill/tool library

  • The PID WHAT I HAVE section could add a new subsection called Operational Assets And Workflows or Working Systems And Reusable Assets so these do not get lost in the strategy sections.

  • For public readability, avoid turning WHAT I HAVE into a raw repo catalog. The strongest pattern is: "I have a working system for X, backed by repos/scripts/workflows Y."

OPEN QUESTIONS FOR YOU

  • Should the public PID describe C:\projects as your "personal operating system," "working project graph," "AI-operable project workspace," or something else?
  • Do you want local reference repos like GBrain/GStack/OpenProse listed as things you are studying/evaluating, or should they be omitted from WHAT I HAVE because they are not your authored assets?
  • How specific should the PID be about edge infrastructure: high-level capability only, or proof points like solar, UPS, recycled hardware, VM inventory, Caddy/Gitea/ops monitor?
  • Should email campaign tooling be framed as an iNDX/LOD internal capability, an open-source template, or both?
  • Do you want the daily operating system and memory-capture flow included publicly, or should it remain private context that only informs future PID updates?
  • Should PTC/SIA proposal work be included now, or only after there is a public outcome?
  • Should LOD operational scripts/processes appear in the PID as "The Light of Dog operational AI systems," or stay out unless they are customer-facing?

SUGGESTED PID Wording Candidates

These are not final edits, just candidate phrasings for the WHAT I HAVE section.

  • "A Git-backed personal operating system under C:\projects that organizes strategy, specs, workflows, scripts, infrastructure, receipts, and project memory into AI-readable repositories."
  • "A reusable structured website builder for the AI era that turns Markdown into fast static websites with semantic chunks, Q&A JSON, JSON-LD, ai-index.json, llms.txt, agents.md, skills.md, sitemaps, robots, and .well-known discovery files."
  • "A private-to-public publication workflow for converting operational repos into sanitized public templates with explicit source gates, anonymization maps, leak scans, validation tiers, ratchet artifacts, and publication receipts."
  • "A multi-brand email/list intelligence stack using Listmonk and Postmark, with export, telemetry pull, non-open analysis, welcome-email, and backup scripts."
  • "A local-first edge compute and resilience stack documented across hardware, software, VM, routing, backup, monitoring, power, and solar-support repos."
  • "A PID/template/skill system for creating and maintaining review-first, evidence-backed portable identity documents as AI-readable identity layers."
  • "A NetworkSIG/PaddleNet strategy and prototype direction for using PIDs, local agents, telemetry, trust, freshness, and permission signals to support agent-mediated matching."
  • "A reusable skill and productivity-tool library that captures repeatable agent workflows, publication processes, product-analysis prompts, bias checks, conversion scripts, and ratchet-based skill design."