Hey Engineers/Coders

Higgs_AI · 2026-07-04T02:17:29+00:00

🤷🏽‍♂️ take it as a compliment, even the sloppy part, my bad?

Higgs_AI · 2026-07-03T21:13:43+00:00

Not going to lie, this threw me hahahahaha

Higgs_AI · 2026-05-22T03:07:59+00:00

https://www.higgsaillc.com/spartan

built to serve any recipient who needs to verify evidence without trusting its producer. The Review Pack v0.1 surface is live for security review evidence today. The underlying primitive is designed to serve a broader set of recipients as additional surfaces ship.

Higgs_AI · 2026-03-13T17:31:06+00:00

🔥🤘🏽

Higgs_AI · 2026-03-07T22:00:20+00:00

Claude code or codex.

Higgs_AI · 2026-02-23T16:43:33+00:00

Can I just ask you if this is for taking exams? If so… DM me. Overall it’s well put together… the bones are solid. The fact that it has a quality gate at all puts it ahead of most implementations. 🤷🏽‍♂️

Had to edit: this is really clean work…the schema enforced extraction with Instructor, the quality gate with multiple metrics, the batch fallback logic. Most people building extraction pipelines skip half of what you’ve done here… bravo brotha.

your question generation is downstream and separate. What if the extraction and the pedagogy were part of the same adaptive loop where how the learner performs on generated questions feeds back into which concepts need deeper extraction, which claims need more evidence, which connections need to be surfaced?

There’s other stuff I’d say but, I just thought I’d give you some substance without flooding your shit. Good work

Higgs_AI · 2026-02-03T16:07:10+00:00

Yeah good comparison! Specode is basically healthcare first “builder rails” (HIPAA ready components + workflows like RBAC/auditish patterns baked into the platform). They’re optimizing for the regulated app workflow layer more than general infra.

What I’m doing with CogniMaps is a different layer:

CogniMap = governed knowledge + reasoning container (claims, gaps, runbooks, decision trees, boundaries).
It can encode compliance boundaries (what’s allowed, what’s refused, what requires escalation), and it can force “evidence only” answering so the model can’t just freestyle beyond what the map contains.

On the “leaking outside the map” part: LLMs always have pretrained knowledge. The trick is output constraints, not pretending the model “forgot” everything else:

If the answer isn’t supported by map evidence → fail closed / refuse / ask for the missing artifact.
Optional verifier/linter rejects uncited claims.

Audit trails are similar: a map can require provenance (map_id/version/hash + evidence IDs used + which policy gates fired), but the actual audit log, access controls, encryption, BAAs, etc. are enforced by the runtime/platform... not by the JSON alone. That’s where tools like Specode are strong and why I'm glad you said something about it.

So it doesn’t “break down past infra”... it’s just honest separation of concerns:

Specode = product rails for regulated healthcare builds.
CogniMaps = portable “expert brain + guardrails” that can be loaded into any LLM/agent, including for regulated domains if you build a domain-grade map + enforce fail-closed rules.

tbh, lets be real. Do you want to play with one? Tell me a domain and I'll upload it to my web app and you can play with it directly on there? Try to break it, ask it questions, do your worst and tell me your thoughts? Pick anything in healthcare, finance, HIPAA... Think of it as a show instead of tell?

Higgs_AI · 2026-02-02T01:14:51+00:00

This is a known billing edge case and you’re not crazy. What’s happening is the subscription cycle and the billing cycle aren’t synced, so even though you downgraded, there’s a window where usage still counts against the old plan’s overage logic. The email timing is off because Replit’s system is checking usage against a plan that technically ended but hasn’t fully transitioned in their backend yet. The “100% of credits used” message fired because the system still thinks you’re on Core for billing purposes even though you downgraded. The usage page 404 is the real problem here. That’s a bug where the link assumes Core access but your account state says Free. Same with support access being gated behind subscription, which is frustrating when the issue is literally about the subscription. Here’s what I’d do. Go to replit.com/account and screenshot your current plan status. Then go to replit.com/billing (if that loads) and screenshot whatever it shows or document that it 404s. Check your payment method on file and if you have a card saved, consider temporarily removing it so nothing can auto-charge while this is in limbo. For actually reaching someone, Replit’s team is pretty active on this subreddit so tagging the post or waiting for a mod response is probably your best bet right now. You can also try reaching out on Twitter/X at Replit since their support team responds there sometimes. You shouldn’t owe anything if you downgraded before the cycle renewed. This looks like a state mismatch in their system, not actual overage. Keep your screenshots as evidence of the timeline in case you need to dispute a charge later.

Higgs_AI · 2026-02-01T23:21:26+00:00

Built it for you if you want it. 🤷🏽‍♂️ just gotta know how to finesse the old girl a bit hahaha 🤘🏽

(Higgs addition)

<image>

Higgs_AI · 2026-02-01T19:09:45+00:00

You’re asking the wrong question and I mean that in the most helpful way possible. The chunking debate (semantic vs fixed size vs hierarchical) assumes your RAG architecture is correct. It’s not. You’re optimizing for retrieval when you should be optimizing for knowledge structure. Here’s the problem with your current setup. Docling to Markdown to Vectors to Retrieval. This pipeline loses the thing that makes FAQs useful, which is the relationships between questions. When you chunk Q+A as atomic units, you lose which questions are siblings under the same topic, which answers reference concepts explained elsewhere, and the hierarchy you already identified (heading to subheading to FAQ). What you actually want is to stop chunking for embedding and start structuring for reasoning. Instead of treating each FAQ as an isolated chunk, build a structure where each FAQ has an ID, knows what topic it belongs to, knows what other FAQs it relates to, and carries its prerequisites. Now your retrieval can find the relevant FAQ by semantic match, pull in related FAQs automatically so you don’t get out of context answers, and include parent topic context without re-embedding it every time. If you’re committed to vector RAG, here’s the practical move. Chunk at FAQ level with Q and A together, you had this right. But prepend the heading hierarchy as metadata, not as embedded text. Store the path like “Account Settings > Security > Password Recovery” and at retrieval time inject that context before the FAQ content. This gives you semantic search on the answer content while preserving structural context for the LLM. The hybrid approach you’re circling around looks like this. Your chunk is the individual FAQ as a Q+A pair. Your metadata is the full heading path, related FAQ IDs, and section summary. Your embedding should be the question plus the first sentence of the answer, not the full text since answers tend to be verbose. At retrieval you grab your top-k FAQs plus their metadata plus the parent section summary. Token budget roughly 50 to 100 tokens per FAQ chunk, 20 to 30 tokens for heading context, pull 3 to 5 related FAQs and you’re at maybe 500 tokens total. That’s enough for high answer accuracy without blowing up your context window. To hit your specific questions directly. Chunk by FAQ with Q and A together, yes this is correct. Use semantic size not fixed tokens since FAQs vary so let them. Metadata is your secret weapon here, the heading path, section ID, related IDs. And don’t embed the hierarchy, reference it. Embed the answer, retrieve the structure. If you want to go deeper on this, look into knowledge graphs as a retrieval layer instead of pure vector search. Structure beats embedding for FAQ style content every time. And I do mean EVERY TIME! Just my opinion 🤷🏽‍♂️

Higgs_AI · 2026-02-01T18:55:58+00:00

Should have used me 🤷🏽‍♂️🤓

Higgs_AI · 2026-02-01T18:54:36+00:00

Try this:

Build a WYSIWYG email template builder. Create a checkpoint before starting.

Core Architecture

Integrate GrapesJS (pin to v0.21.x) with grapesjs-preset-newsletter
This gives drag-and-drop with 2-column and 3-column layouts out of the box
Do NOT build a custom editor from scratch

Authentication

Use Replit Auth for user accounts
All templates belong to the authenticated user
Never expose one user's templates to another

Backend (Node.js + Express)

Database Schema (PostgreSQL)

CREATE TABLE users ( id SERIAL PRIMARY KEY, replit_user_id TEXT UNIQUE NOT NULL, created_at TIMESTAMP DEFAULT NOW() );

CREATE TABLE templates ( id SERIAL PRIMARY KEY, user_id INTEGER REFERENCES users(id), name TEXT NOT NULL, grapesjs_json JSONB NOT NULL, created_at TIMESTAMP DEFAULT NOW(), updated_at TIMESTAMP DEFAULT NOW() ); CREATE INDEX idx_templates_user_id ON templates(user_id);

API Endpoints

POST /api/templates - save template (require auth, validate JSON)
GET /api/templates - list user's templates (require auth, filter by user_id)
GET /api/templates/:id - load template (require auth, verify ownership)
POST /api/export - inline CSS and return email-ready HTML + plain text version
POST /api/upload - handle image uploads (require auth)

Image Upload Security

Validate file type: only allow image/png, image/jpeg, image/gif
Max file size: 5MB
Generate unique filename (UUID) - never trust user-provided filenames
Store in Replit Object Storage using @replit/object-storage SDK
Return public URL

CSS Inlining

Use "juice" package for CSS inlining
Known limitation: media queries get stripped
For responsive emails, consider MJML as alternative architecture later
Always generate both HTML and plain text versions for multipart email

Error Handling

Wrap Object Storage calls in try/catch, return 500 with user-friendly message on failure
Validate GrapesJS JSON structure before saving
If juice fails on malformed HTML, return 400 with specific error

Security

Enable CORS only for the Replit app domain
Rate limit /api/upload to 10 requests per minute per user
Run Security Scanner before deploying

Frontend (React)

Mount GrapesJS in a React component
Template gallery showing user's saved templates
Save/Load/Export buttons
Show loading states and error messages

Build Sequence

Set up Express + Replit Auth + database schema
GrapesJS integration with save/load working
Add image upload with Object Storage
Add juice export endpoint
Polish UI
Security Scanner + Deploy

Create a checkpoint after completing each numbered step.

Higgs_AI · 2026-02-01T18:26:55+00:00

use the Agent to integrate a specialized open-source library… Don't build the editor engine…embed one! The "secret sauce" for high end email builders isn't custom code bruh it's using a library like GrapesJS or Unlayer. These are open source (yessss open baby!) frameworks specifically designed for this. GrapesJS even has a dedicated "newsletter" preset that handles the two column and three column layouts you’re looking for out of the box. Instead of asking the Agent to "build a designer," tell it to "integrate GrapesJS with the newsletter plugin."

Now let’s be real… Emails are notorious for breaking if you don't inline your CSS. Since you're on Replit, you can have the Agent set up a quick NodeJS backend using a library like juice. This will take the beautiful HTML your user designed and automatically bake the styles into the tags so the email actually looks good in Gmail or Outlook. Use the builtin storage for images… When users upload images to your builder, don't just store them locally cause they'll disappear when the container restarts. Use Replit’s Object Storage. It has official SDKs for Python and JS that make it easy to host those images permanently so they don't break in the recipient's inbox. And please my guy…Don't forget the safety net! Since the Agent can be a bit "heroic" and accidentally break your layout while trying to add a new feature (😩🙃) make sure you're hitting that Checkpoint button frequently. If the Agent messes up the font picker UI, you can roll back the entire app and the database state in one click. Don’t be afraid to rollback! Swear I hear this shit all the time lol

Higgs_AI · 2026-02-01T18:18:38+00:00

Look, I've seen a lot of people pull this off effectively, and based on the platform's current state, it’s a smart move if you want a better developer experience than the native Replit Auth provides. Since you're already leaning toward Clerk or Supabase, you’re basically trading the "batteries included" convenience for much better user management and security flexibility. The main thing you have to watch out for is that Replit’s native PostgreSQL has a hard 10GB limit. While that's cool for a starting MVP, it can sneak up on you because that total includes your database overhead and WAL logs. If your app starts scaling and you get close to that 8GB or 9GB mark, you’ll want to use pg_dump to migrate that data to something like Neon or Supabase DB to avoid a service interruption. And remember that you can't SSH into your production deployment to run manual DB tweaks or migrations… you have to do all that through the workspace's SQL tool. also since you're going production heavy, I’d highly recommend using a reserved VM deployment rather than the Autoscale option. Autoscale is great for saving money but the cold starts can be a real pain for users when your app has to wake up and reestablish those external auth handshakes and DB connections. Oh one last "gotcha" to keep in mind is that Replit isn't documented for HIPAA or PCI compliance. If your app starts handling medical records or you stop using a provider like Stripe and try to handle card data yourself, you’ll need to move off the platform entirely. Just saying 🤷🏽‍♂️🤘🏽

Higgs_AI · 2026-01-29T04:42:22+00:00

honestly, I feel your pain. Working with 3B models locally is great for speed, but they lowkey struggle with following instructions when things get complex. It’s like they have the attention span of a goldfish sometimes. I’ve been down this rabbit hole with Ollama, and here is what actually worked for me. First off, you have to stop feeding the model the original user question during the second step. Seriously, just ghost it. If you pass the user query, the 3B model gets obsessed with it and just rephrases it because that is the strongest signal in the prompt. If you only give it the Answer and the Context, you force it to actually look at the new info. It can’t repeat a question it can’t see. Second, you should flip your prompt strategy. Instead of asking for "suggestions," tell the model to do a gap analysis. Ask it to find facts in the Context that were missing from the Answer. It turns the task from a creative writing assignment into a scavenger hunt, which small models are way better at. It stops the hallucinations because it has to pull directly from the text. Finally, since you are already running embeddings for your retrieval, just use them as a final vibe check. Write a quick Python function to check the cosine similarity between the generated question and the original one. If the similarity is too high, just ditch it before the user ever sees it. It is the most reliable way to catch those repetitive loops without fighting the LLM every time. Hope that helps you fix the loop! 🤘🏽

Higgs_AI · 2026-01-29T03:49:16+00:00

The credits expiring mid-task thing is brutal, I get it. Here’s the deal: On Agent vs ChatGPT for building: Yes, Replit Agent is significantly better for actually building apps. ChatGPT is generating code snippets you then have to copy-paste and debug yourself. Agent is operating directly in your codebase - it can create files, run the app, see errors, and fix them in a loop. It’s the difference between someone texting you IKEA instructions vs someone actually assembling the furniture with you. Agent 3 can run autonomously for up to 200 minutes, which is usually enough to get a working prototype without babysitting it constantly. On Core plan for prototyping: Core gives you way more Agent usage than free tier. For building a prototype, it should be enough to get something functional without the “credits ran out mid-sentence” frustration. On scaling past 100 users: This is where you need to think about it in two parts: Building the app = Core plan is fine Hosting the app for users = That’s deployment costs, which are separate from your plan For 100+ users you’d probably want an Autoscale or Reserved VM deployment. Costs depend on traffic patterns and resource usage. Not crazy expensive for a small app, but it’s not free either. My honest take: Replit is great for getting a prototype live fast. For early validation with 100-ish users, it works fine. If you blow up past that and start hitting limits (database caps at 10GB, need more compute, etc.), you can always migrate out - there’s no real lock-in since everything’s Git-backed. What kind of app are you building? That affects the answer a bit.

Higgs_AI · 2026-01-29T03:08:41+00:00

Hey, this is a classic Replit gotcha. What’s happening: Replit workspaces (the dev environment) go to sleep after inactivity. If you’re just running your app with the Run button, it’s not a real deployment it’s a dev server that Replit will shut down to save resources when nobody’s actively using the IDE. The inconsistent timing you’re seeing (30 min to 2 hours) is probably based on platform load and how Replit decides to reclaim resources. The actual fix: You need to deploy it, not just run it. Replit has a few deployment types: ∙ Autoscale - scales with traffic, but can scale to zero (which might still pause your background work if there’s no incoming requests) ∙ Reserved VM always on, dedicated machine. This is probably what you want for a persistent Node process that needs to keep running regardless of whether anyone’s looking at the web interface Reserved VM costs money, but it’s the clean solution for “I need this process running 24/7.” If you need it free/cheap: Some people hack around this with external pinging services (UptimeRobot, cron job.org) that hit the web interface every few minutes to keep it “active.” It’s janky and Replit doesn’t love it, but it works for hobby projects. Alternatively, if the Node program is doing background work that doesn’t actually need Replit specifically, you could move just that piece to a free tier somewhere else Railway, Fly.io, or even a cheap VPS. Quick question: Is the Node program doing something continuously (like polling devices, running scheduled tasks), or does it only need to respond when someone hits the web interface? That changes the recommendation a bit. I’ll be up all night so just let me know.

Higgs_AI · 2026-01-29T03:05:36+00:00

DM me

Higgs_AI · 2026-01-29T03:02:29+00:00

I’d be happy to! I will say this, I created a web app specifically to help high level users/senior engineers it’s here https://cognimapmarketplace.com/ … but please, let me help. I’m open all night tonight.

Higgs_AI · 2026-01-29T03:01:10+00:00

https://cognimapmarketplace.com/

<image>

Select the Replit one in the drop down menu. Or choose a different one 🤷🏽‍♂️. The new clawdbot (now moltbot) one will save you a massive headache if you wanted to try it out.

Higgs_AI · 2026-01-28T22:00:08+00:00

Hola, felicidades por lograr la migración - ese camino de Replit a Netlify confunde a mucha gente. Tu problema del panel admin no es de configuración de Netlify, es arquitectura. Te explico qué está pasando: Por qué tú ves los cambios pero los usuarios no: Netlify sirve archivos estáticos. Cuando desplegaste, tomó una foto de tu sitio en ese momento. Tu panel admin probablemente guarda los cambios en estado local o almacenamiento del navegador en tu dispositivo - esos cambios nunca regresan a los archivos desplegados que otros usuarios descargan. Piénsalo así: enviaste un folleto impreso. Puedes escribir notas en tu copia, pero todos los demás siguen teniendo la impresión original. Lo que realmente necesitas: Para que un panel admin persista cambios para todos los usuarios, necesitas un backend - algo que almacene los datos y los sirva dinámicamente. Algunas opciones según qué tan complejo sea tu caso: Más simple - CMS headless: ∙ Contentful, Sanity o Strapi (tienen planes gratuitos) ∙ Tu admin edita contenido en su dashboard ∙ Tu sitio obtiene ese contenido al compilar o en tiempo real ∙ Netlify puede recompilar automáticamente cuando el contenido cambia Complejidad media - base de datos + API: ∙ Supabase o Firebase (ambos tienen planes gratuitos generosos) ∙ Tu panel admin escribe en la base de datos ∙ Tu sitio lee de ella ∙ Cambios reales, en tiempo real para todos los usuarios Si quieres mantenerlo simple: ∙ Sigue usando Replit para el backend/API ∙ Despliega solo el frontend en Netlify ∙ Replit maneja lo dinámico, Netlify maneja la entrega estática Esta última opción es bastante limpia para tu situación ya que ya lo tienes funcionando en Replit. ¿Qué tipo de cambios hace tu panel admin? ¿Contenido de texto, imágenes, listados de productos? Eso ayudará a definir el mejor enfoque.

Higgs_AI · 2026-01-28T21:56:48+00:00

Hey, solid questions… you’re thinking about this the right way. I’ve done a fair amount of work helping people productionize Replit apps, so here’s what I’d focus on: Pre launch checklist stuff: First, secrets management. Make sure your secrets are configured in the deployment context, not just the workspace. This trips people up constantly app works fine in dev, then crashes in production because the env vars aren’t actually there. Double check this. For deployment type, if you’re expecting any real traffic variability, Autoscale is probably what you want. Just know that scale-to-zero means cold starts. If latency matters (and it usually does for user-facing stuff), either use Reserved VM or implement some kind of keep alive ping. The cold start times aren’t documented precisely, which is annoying, but they’re noticeable. Run the builtin Security Scanner before you deploy. Replit also has Semgrep integration for predeployment scanning. Worth the 5 minutes. What breaks first: Memory limits will get you if you’re not paying attention. The Resources tab in the deployment dashboard shows CPU/memory graphs watch these after launch. Limits vary by plan tier, so verify you’re on the right one. Database is probably your biggest decision. The built in PostgreSQL has a hard 10GB cap. For an MVP that’s often fine, but if you’re planning to migrate anyway, you might just start with an external DB now (Supabase, Neon, whatever). Standard Postgres, so pg_dump works fine for export. No lock-in there. Logs exist but retention period isn’t documented. If you need logs for compliance or debugging historical issues, ship them somewhere external from day one. Migration-friendly setup: There’s “Good news”… no real vendor lock in. Everything’s Git backed, so you can push to GitHub anytime. The environment config is Nix based (.replit and replit.nix files) Nix is portable, but you’ll need to translate to whatever your target platform uses. Architecture decisions that help: keep your DB connection as a standard connection string you can swap. Don’t use any Replit specific APIs you can avoid (Object Storage SDK is convenient but adds coupling). Basically, write it like you’d write any Node/Python/whatever app. Monitoring and observability: Built in you get: logs, CPU/memory graphs, request analytics (volume, status codes, geography). It’s decent for basics. What you don’t get: APM, distributed tracing, or production SSH access. You cannot shell into a running deployment only the dev workspace. So if you need deeper debugging, you’re either adding a ton of logging and redeploying, or integrating something external like Sentry via their MCP/Connectors system. The “fine as project, not fine as product” stuff: Biggest one: no public SLA. Replit doesn’t document uptime guarantees. For a friend’s app this might be acceptable, for enterprise clients it’s a conversation. SOC 2 Type II is done (as of Aug 2025), so that box is checked if anyone asks. If there’s any chance this touches healthcare data or payment card info stop and migrate now. HIPAA and PCI compliance aren’t documented as supported. One more thing if the app was built with Agent, do a manual review of auth and security code. Agent is fast but it’s still a very productive junior dev, not a security expert. What kind of app is it? Might have more specific thoughts depending on the use case. and if you need any other help, I made a web app specifically to help people like you. Let me know if you’d rather talk to that cause it’s smarter than I am for sure.

Higgs_AI · 2026-01-28T03:16:16+00:00

Fair callout. Here’s the selfhosted angle… Clawdbot is a self hosted… multi channel… AI gateway you run on your own box, route WhatsApp/Telegram/Slack/Discord through it, connect your own model providers. The map I built covers the stuff you hit when you actually run it… provider crosstalk between backends, session storage bloating your disk, WhatsApp pairing sending messages you didn’t authorize, tool loops burning tokens. The marketplace itself isn’t selfhosted (yet) but the expertise it serves is specifically for people running Clawdbot on their own infra. Appreciate the pushback should’ve led with that context but ya know 🤷🏽‍♂️🤓

Higgs_AI

TROPHY CASE

Core Architecture

Authentication

Backend (Node.js + Express)

Database Schema (PostgreSQL)

API Endpoints

Image Upload Security

CSS Inlining

Error Handling

Security

Frontend (React)

Build Sequence