Public summary
Public-safe summary is available for discovery, but it is not a substitute for diligence.
Responsible use
Review the portfolio through evidence, safety, and controlled access.
A public-safe trust and review posture for buyers, partners, and implementation teams evaluating software assets across sensitive workflows, AI-assisted use cases, and transfer conversations.
Responsible-use posture
Public-safe review without pretending the public page is diligence.
This page separates what buyers can safely browse from the materials that require app-specific fit, safety, and access review.
18
Public signals
Discovery-level evidence available across app records.
35
Gated signals
Materials or details that require controlled review.
31
Verify
Items that should be checked before buyer reliance.
Safety before scale
Sensitive workflows are reviewed through harm-reduction, privacy, and human-accountability boundaries before broader use.
Evidence by app
Readiness is evaluated app by app across docs, testing, data handling, transfer, and known gaps.
Controlled materials
Public pages are safe for discovery; sensitive technical and commercial details are shared only after fit review.
Safe to browse publicly
Public pages are for discovery.
These items help a buyer understand purpose, fit, readiness, and whether a deeper review is worth requesting.
- Product summaries
- Use cases and buyer fit
- High-level capabilities
- Stage and readiness labels
- Public-safe evidence posture
Shared after review
Diligence materials are not self-service.
Sensitive implementation detail is shared only when the request, asset, and intended use are appropriate.
- Technical and operational review materials
- App-specific diligence notes
- Transfer and implementation context
- Safety and data-handling notes
- Commercial discussion materials
- Scoped app review materials
Canonical readiness taxonomy
One public vocabulary for maturity and review posture.
Public-safe summary
Discovery-level information that explains purpose, audience, and constraints without exposing controlled materials.
Not a substitute for app-specific diligence or implementation planning.
Review-ready
Enough public and gated context exists for a qualified reviewer to evaluate fit, gaps, and next steps.
Access to deeper materials depends on fit review.
Controlled pilot-ready
Appropriate for scoped pilot conversations with human oversight, defined boundaries, and implementation review.
Pilot suitability must be confirmed against the intended use and operating context.
Technical preview
A working preview whose next readiness gate, public access posture, validation evidence, and deployment authority remain pending.
Gate 1, independent validation, and production-host authority are still pending.
License-ready
Documented enough to discuss licensing with qualified buyers or partners.
License terms, support scope, and implementation obligations require written agreement.
Active hardening
Useful functionality exists, with remaining product, test, documentation, or operational work tracked before broader reliance.
Showcase-only
Presented as a portfolio example or concept demonstration rather than a deployable product path.
Do not treat as ready for broader reliance without a new review.
Concept-stage
Early product concept or exploratory asset requiring substantial validation before buyer reliance.
Portfolio evidence dashboard
Every asset gets its own review posture.
Status cards distinguish public summaries, controlled-review materials, and items that require verification before buyer reliance. Several tracked assets include AI, LLM, or Gemini-assisted workflows, so evidence and controlled-access labels are reviewed app by app.
License-readyReview-ready
CallCraft
CallCraft is a pre-revenue software IP asset that combines an implemented training platform with a versioned scenario library, simulated caller personas, structured coaching reviews, supervisor-facing reporting, and organizational administration.
3
Public signals
2
Gated items
1
Needs verification
Evidence
Public evidencePublic summary
DocumentationPublic summary
Test / QAPublic summary
Data / privacyApp-specific
Transfer / licensingRequest required
Demo / disclosureRequest required
Pilot-readyDiligence-ready
Protectly
Protectly is a controlled-review Texas protective-order drafting platform with survivor intake, advocate review, admin oversight, AI-assisted drafting support, document export, backend-mediated draft sync, and state e-filing simulation. It is controlled-review and pilot-oriented under qualified operator conditions, but not represented as a public launch, legal service, production data system, or proven live court-filing operation until database security rules, storage security rules, current automated testing, target-environment readiness, legal, privacy, safety, accessibility, monitoring, backup/restore, and e-filing credential validation are complete.
1
Public signals
3
Gated items
2
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureRequest required
Technical previewActive hardening
EchoCheck
EchoCheck is a pre-revenue technical-preview platform for structured AI response evaluation in DV/IPV and survivor-serving contexts. It runs the same simulated request through five prompt configurations, applies a schema-validated 12-dimension evaluation layer, and creates review records for qualified human analysis. Gate 1 approval, independent subject-matter validation, approved production host, and live-environment verification remain pending.
1
Public signals
3
Gated items
2
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureRequest required
Active hardeningActive hardening
BIPP Training Simulator
BIPP Training Simulator is an implemented practice platform for Battering Intervention and Prevention Program facilitators. It combines fictional scenarios, text and voice interaction paths, saved sessions, draft after-action feedback, supervisor review, reporting, and administrative tools.
1
Public signals
3
Gated items
2
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureRequest required
Active hardeningActive hardening
DeckSpeak
DeckSpeak is an implemented presentation platform that turns PDF, DOCX, TXT, markdown, and pasted text into reviewable decks with speaker notes, source references, visual planning, presenter controls, typed and voice assistance, and multiple export formats.
1
Public signals
3
Gated items
2
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureRequest required
Active hardeningActive hardening
GrantWise
GrantWise is an active-hardening SaaS application for AI-assisted grant analysis, compliance checking, requirement tracking, knowledge retrieval, and section drafting. It turns complex NOFOs, RFPs, companion guides, and organizational source materials into structured requirements, readiness metrics, policy-gap findings, evidence links, and draft narrative sections.
1
Public signals
2
Gated items
3
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureApp-specific
Active hardeningActive hardening
IdeaForge Critic
IdeaForge Critic is an active-hardening AI critique platform for startup ideas, grant proposals, strategy documents, and product concepts. It combines 15+ critique mode personas, boardroom-style expert orchestration, Clarification Gate, research-assisted critique, grant document-set intelligence, requirement extraction, evidence-anchored grant review, session persistence, export, telemetry, secure authentication and data storage, and a backend proxy for AI access.
1
Public signals
3
Gated items
2
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureRequest required
Active hardeningActive hardening
SeededPath
SeededPath, also described in the connected repo as SeededPath (Beacon of Hope), is an active-hardening survivor-safety and resource hub for domestic violence contexts. It combines safety planning, smart-device disconnector guidance, Texas legal and resource content, assessments, evidence and journal tools, AI-assisted document and guide generation, anonymous mode, Quick Exit, Local Erase, local vault patterns, user-owned backend data paths, and AI-assisted flows. Public-facing claims should be privacy-bounded and validated before survivor-facing launch.
1
Public signals
2
Gated items
3
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureNot publicly listed
Active hardeningActive hardening
SpeakerFree
SpeakerFree is an active-hardening smart-home safety guidance tool for survivors dealing with technology-enabled abuse. It combines safety-context intake, device selection, AI-assisted plan generation through a gateway pattern with fallback endpoints, image-analysis flow, Bluetooth scanning, quick exit, camouflage mode, and minimized local-state handling. It should be evaluated as a safety-focused technical prototype that needs security, privacy, testing, and launch validation before high-risk public use.
1
Public signals
2
Gated items
3
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureNot publicly listed
Active hardeningActive hardening
Texas Legislature Tracker
Texas Legislature Tracker is an implemented policy-intelligence platform for Texas advocacy teams. It organizes public bill, legislator, committee, hearing, and district information, then connects that context to saved tracking, twelve AI-assisted analysis and drafting tools, and campaign preparation workflows. The product is in active hardening and requires current deployment, data-freshness, security, and release verification before production reliance.
1
Public signals
3
Gated items
2
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureRequest required
Active hardeningActive hardening
Texas TDV Resource Hub
Texas TDV Resource Hub is an active-hardening MVP for school-safety and teen dating violence resource intelligence across Texas districts. It combines a browser-based dashboard with a backend service, AI-assisted district research, policy audit support, district profile views, reporting surfaces, database-backed saved comparisons, and controlled demo workflows. It should be positioned for controlled review, buyer diligence, or pilot planning rather than public launch until live data sources, security testing, SME review, legal review, privacy review, accessibility, and launch evidence are verified.
1
Public signals
2
Gated items
3
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureNot publicly listed
Active hardeningActive hardening
Zoe
Zoe 3.1 is an implemented meeting workspace with authenticated session hosting, voice interaction, transcript capture, uploaded document and image context, action items, analysis, charts, exports, and feedback collection.
1
Public signals
2
Gated items
3
Needs verification
Evidence
Public evidenceGated review
DocumentationPartial
Test / QAPartial
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureApp-specific
PrototypeActive hardening
Bloom Remix
Bloom Remix explores a wellness-first interface that can support private documentation workflows in controlled review settings using mock or approved training content only.
2
Public signals
3
Gated items
1
Needs verification
Evidence
Public evidenceGated review
DocumentationPublic summary
Test / QANeeds verification
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureRequest required
PrototypeActive hardening
Survivor Safety Sentinel
Survivor Safety Sentinel is a controlled-review browser-based prototype for domestic violence survivor risk reflection and safety planning. It combines local assessment workflows for danger, lethality, stalking, technology abuse, economic abuse, reproductive coercion, and readiness for change with a context-aware safety plan wizard, grounding support, Quick Exit, local erase, privacy pause, masked plan view, safety library resources, and AI-assisted assessment analysis and safety-plan generation. It should be positioned for private diligence or controlled pilot planning only until AI credential handling, data privacy, security, legal, clinical, accessibility, and survivor-safety validation are complete.
2
Public signals
2
Gated items
2
Needs verification
Evidence
Public evidenceGated review
DocumentationPublic summary
Test / QANeeds verification
Data / privacyPublic summary
Transfer / licensingGated review
Demo / disclosureNot publicly listed
Responsible-use principles
Operating boundaries that travel with the work.
These principles define how sensitive workflows, buyer review, AI assistance, documentation, and transfer readiness are framed across the portfolio.
Safety before scale
ActiveApps connected to survivor safety, crisis training, legal support, or sensitive nonprofit workflows are reviewed with harm reduction, privacy, and safe-use boundaries in mind before broader deployment or transfer.
App-level evidence
ActiveEach app is evaluated on its own architecture, data handling, testing, documentation, integrations, deployment model, and known gaps. A strong claim for one app is not treated as a blanket claim across the portfolio.
Data minimization
ActivePortfolio apps are designed to avoid unnecessary personal information and to keep sensitive workflows as narrow as possible. Where data storage, authentication, or third-party processing exists, it should be reviewed in the app-specific controlled review materials.
Human review by design
ActiveAI-assisted tools are positioned as support systems for drafting, training, analysis, triage, critique, or workflow acceleration. They are not substitutes for legal advice, survivor advocacy, clinical judgment, financial approval, or organizational accountability.
Honest readiness
ActiveApps may be license-ready, in active hardening, in beta, prototype-stage, or showcase-only. Readiness labels are intended to make the review process clearer, not to flatten meaningful differences between assets.
Documentation-first transfer
In progressReview notes, data-handling summaries, roadmap items, transfer scope, and known limitations are organized so buyers and partners can evaluate each app with less ambiguity.
AI and sensitive-use review
Safety claims stay specific to the use case.
AI-assisted workflows
Human review by design
Decision support, not final authority
AI-generated outputs are framed as drafts, simulations, recommendations, critiques, summaries, or training aids. Final decisions remain with responsible people and organizations.
Human-in-the-loop review
Sensitive workflows should include review by advocates, legal professionals, administrators, trainers, finance staff, grant managers, or other qualified users as appropriate.
Prompt and output safeguards
AI apps should be reviewed for prompt boundaries, misuse scenarios, redaction behavior, hallucination risk, citation quality, and output consistency.
Clear limits
Apps should not imply legal, clinical, safety, or financial authority unless that authority exists outside the software through the user's professional role and organizational process.
Context-aware risk review
A grant parser, crisis training simulator, legal drafting assistant, and survivor safety guide carry different risks. AI safety review should match the app's actual use case.
Sensitive-use design
Harm-reduction defaults
Plain-language boundaries
Sensitive-use apps should clearly explain what the tool can do, what it cannot do, and when the user should seek qualified support.
Privacy-aware workflows
Apps should avoid collecting details that are not needed and should be reviewed for storage, browser history, exports, notifications, and device-safety implications.
No victim-blaming design
Language and workflows should avoid implying that responsibility for abuse, system barriers, or safety risk rests with the survivor or user.
Safe escalation
Tools that surface risk should route users toward appropriate human support, local policy, organizational protocol, or qualified review instead of presenting software output as a final answer.
Training realism with care
Simulation tools should help staff practice difficult conversations without exposing real people, real survivor details, or unnecessary graphic content.
Review categories
What public, gated, and verification labels mean.
Data handling and privacy
Public
Public app pages may summarize the data-handling posture when a safe summary exists.
App review
Inputs, outputs, storage, retention, logs, exports, third-party processing, and deletion paths are reviewed per app.
Gated
Sensitive data maps, implementation details, screenshots, and private workflow notes stay gated.
Verify
Confirm current behavior before relying on privacy or data-minimization claims.
Security and access
Public
Public pages describe security posture only at a high level where supported.
App review
Authentication, roles, Credential handling, tenant boundaries, rate limits, monitoring, and dependency posture are app-specific.
Gated
Sensitive technical, access, deployment, and security details are controlled-review materials.
Verify
Confirm implementation, environment configuration, and current dependency posture before deployment decisions.
AI safety and survivor-safety review
Public
Public copy identifies intended use and safety boundaries without exposing sensitive prompts or workflows.
App review
AI-assisted tools are reviewed for human oversight, misuse risk, redaction needs, output limits, and survivor-safety context.
Gated
Prompt details, red-team notes, sensitive simulations, and private walkthroughs may require controlled review.
Verify
Confirm safeguards and review expectations in the context of the intended implementation.
Documentation and handoff
Public
Public app records may show documentation labels, tables of contents, and setup posture summaries.
App review
Implementation notes, operating guidance, transfer notes, and roadmap details are reviewed app by app.
Gated
Detailed handoff and implementation materials are shared selectively.
Verify
Confirm documentation currency and completeness before buyer reliance.
Testing and QA
Public
Public records may list test posture summaries where canonical data includes them.
App review
Linting, type checks, build status, unit tests, smoke tests, e2e tests, coverage, and current pass status require app-specific review.
Gated
Raw reports, private test runs, and code-path coverage details may require controlled review.
Verify
Confirm current test results and gaps before treating an app as implementation-ready.
Transfer and licensing
Public
Public pages may list commercial options and acquisition-readiness labels from canonical app records.
App review
Transfer scope, included assets, licensing path, support expectations, and implementation assumptions are discussed per app.
Gated
Commercial terms, transfer materials, repository handoff detail, and private controlled review materials are not self-service.
Verify
Confirm transfer scope and licensing terms before transaction planning.
Diligence and disclosure
Public
Public pages provide discovery-level evidence posture and links into app-specific review paths.
App review
Request context, intended use, mission fit, risk profile, and access level determine what can be shared.
Gated
Sensitive materials are shared only after controlled review and appropriate terms where needed.
Verify
Buyer reliance requires app-specific diligence; public summaries are not exhaustive controlled review materials.
Evidence status legend
How to read the dashboard.
Labels are intentionally conservative. They describe public evidence posture and whether buyer reliance requires additional review.
Gated review
Details may be shared after review when the request, app, and intended use are appropriate.
Needs verification
Current posture should be confirmed before buyer reliance or implementation planning.
Not publicly listed
No public detail is listed; ask through controlled review if it is relevant to your evaluation.
Request required
Materials or walkthroughs may be available through controlled review when appropriate.
Partial
Some evidence exists, but not enough for broad claims without app-specific verification.
App-specific
The answer depends on the app, use case, implementation context, and current readiness.
Buyer review checklist
A practical review sequence.
01
Confirm app stage and acquisition-readiness label.
02
Review the app-specific evidence panel on the app detail page.
03
Confirm documentation posture and what remains gated.
04
Confirm test and QA posture before implementation reliance.
05
Review data-handling boundaries and sensitive-use context.
06
Identify technical, security, demo, or transfer materials needed for app review.
07
Submit a controlled diligence request for app-specific materials.
08
Discuss transfer, licensing, implementation, or acquisition scope after fit is established.
Controlled diligence path
Materials are released through a scoped review flow.
01
Initial request
A buyer, funder, partner, or implementation lead submits an inquiry identifying the apps and goals they want to discuss.
02
Fit and safety review
The request is reviewed for mission fit, intended use, safety considerations, and whether the app is appropriate for acquisition, licensing, partnership, pilot, or custom deployment.
03
Access terms
Sensitive technical materials may require an NDA, written access terms, or a scoped review agreement.
04
App-specific packet
Reviewers may receive scoped product, technical, data-handling, roadmap, limitation, and transfer materials.
05
Technical and product review
Review may include code walkthroughs, local setup, dependency review, test posture, documentation review, security posture, AI behavior, and deployment-readiness assessment.
06
Remediation or transaction plan
Any open issues are documented with recommended next steps before production use, licensing, transfer, or acquisition.
Evidence packet categories
What buyers may request
Product overview
Purpose, user audience, buyer fit, screenshots, demo notes, use cases, and limitations.
Architecture
High-level system design, integration boundaries, access model, and dependency posture.
Data handling
Inputs, outputs, storage, retention, exports, logs, deletion paths, access controls, and third-party processing.
Test posture
Linting, type checks, unit tests, smoke tests, e2e tests, build validation, coverage notes, and known gaps.
Security posture
Credential handling, rate limiting, role-based access, access review, AI safeguards, abuse controls, and operational risks.
Documentation
Implementation notes, operating guidance, workflow notes, user flows, transfer notes, and roadmap.
Known gaps
Prototype limitations, missing production controls, incomplete integrations, manual processes, deployment risks, or documentation gaps.
Transfer scope
Repository transfer scope, deployment guidance, support period, licensing terms, acquisition terms, and transition support.
Review notes
Readiness varies by app
A license-ready app should not be evaluated the same way as a prototype, private beta, or showcase concept.
Each app includes a stage, acquisition-readiness level, roadmap, known gaps, and recommended review path.
Security posture is app-specific
Some apps include stronger backend controls, monitoring, tenant handling, or test coverage than others.
Controls should be verified against each app's repo, docs, deployment model, and current code.
Data handling differs by use case
A crisis training simulator, legal drafting tool, grant parser, and presentation tool have different privacy needs.
Data handling should be reviewed per app, including inputs, storage, exports, retention, third-party APIs, and user access.
AI safeguards need context
Prompt boundaries, redaction, grounding, simulation behavior, and output review differ by app.
AI-assisted apps should be reviewed for intended use, misuse risk, human review, and output limitations.
Production hardening may still be needed
Some apps may need monitoring, error reporting, multitenancy, tenant controls, audit logs, backup planning, or deployment cleanup before broader use.
Hardening needs should be disclosed in each app's controlled review materials.
Public summaries are not full diligence
Portfolio pages are designed for discovery and buyer screening, not exhaustive technical review.
Detailed materials are shared through controlled app-specific review.
Security and operational controls
Controls are app-specific and verified before production reliance.
PII minimization
Active principleConfirm the app only requests information needed for the workflow and avoids unnecessary sensitive details.
Sensitive workflow boundaries
Active principleConfirm the app clearly states what it does, what it does not do, and when a qualified human should review the output.
Credential handling
App-specificConfirm whether provider credentials are protected appropriately for the app context.
Authentication and access control
App-specificConfirm login model, user roles, admin access, row-level security, tenant boundaries, and access revocation where relevant.
Data storage and retention
App-specificConfirm what is stored, where it is stored, who can access it, how long it remains available, and how it can be deleted or transferred.
Rate limiting and abuse controls
App-specificConfirm throttling, abuse prevention, prompt-injection defenses, upload limits, and safeguards for high-cost or high-risk workflows.
Monitoring and error reporting
App-specificConfirm whether production operations are observable and supportable.
Dependency governance
In progressConfirm dependency inventory, update posture, known vulnerabilities, and software composition review before production use.
Auditability
App-specific or plannedConfirm logs for approvals, access changes, document generation, data exports, admin actions, and other sensitive events where needed.
Deployment configuration
App-specificConfirm deployment configuration, secrets management, backup expectations, and recovery approach.
Controlled diligence
Ready to review a specific app responsibly?
Start with the public portfolio, then request app-specific controlled review materials when you know what evidence, review scope, or transfer discussion you need.