DEV Community: kyisaiah47

CivicBinder scans public websites and turns findings into a repair binder

kyisaiah47 — Tue, 29 Sep 2026 20:47:17 +0000

CivicBinder's fulfillment lane stopped after repeated network failures because Node was choosing DNS addresses in an unstable order. Commit ad21608 fixed the failure by setting IPv4-first resolution before the helper's network calls. The live CivicBinder page shows what that work produces: a scan, a document inventory, policy and statement text, and a dated remediation plan.

CivicBinder

Accessibility evaluation

The main page describes an automated WCAG 2.1 AA evaluation covering up to 150 pages and 100 PDFs, with findings ranked by severity.

The evaluation turns scan results into findings that can be explained and handed to the person responsible for repairs.

Document inventory

The binder outline includes a document inventory covering every PDF on the site and its accessibility status.

The inventory keeps documents inside the same dated scope as the page scan, so the binder records what was checked rather than only describing the website generally.

png)

Accessibility Policy

The live binder outline includes an Accessibility Policy prepared for adoption by the governing body.

The policy gives the entity a document it can take through its regular meeting process instead of leaving the scan as a standalone technical report.

Accessibility Statement

The binder includes an Accessibility Statement ready to publish, with a feedback mechanism.

The statement turns the findings into public-facing text and gives visitors a route for reporting accessibility problems.

png)

Remediation plan

The binder outline includes a dated, phased remediation plan described as vendor-executable.

The plan orders repairs by severity and gives the work a schedule tied to the scan and the entity's applicable Title II date.

Pages evaluated

The binder includes an appendix listing the pages and documents in scope, along with the scan date.

That appendix limits the claim to the material CivicBinder actually evaluated, which makes the resulting record specific to the site state captured by the scan.

Fulfillment network helper

The commit named ad21608 changed ops/fulfill/services.mjs after the fulfillment lane exited with the same failure code repeatedly. The commit message identifies unstable DNS address ordering as the cause.

 import { readFileSync, writeFileSync, existsSync, chmodSync } from 'node:fs';
 import { execFileSync } from 'node:child_process';
+import { setDefaultResultOrder } from 'node:dns';
 import { join, dirname } from 'node:path';
 import { fileURLToPath } from 'node:url';

export const HERE = dirname(fileURLToPath(import.meta.url));
+setDefaultResultOrder('ipv4first');
 const ENV_CACHE = join(HERE, '.env');

The fix sets Node's default DNS result order before the helper reaches its network calls. I kept the change at the helper boundary, where the failure occurred, and left the fulfillment operations around it unchanged.

Four AI agents that leave a human approval step

kyisaiah47 — Mon, 28 Sep 2026 20:31:54 +0000

This issue follows four AI agents that leave a human approval step before a write, retry, reply, or send. Their pages show what each agent reads, what it produces, and where a person can still stop the action.

Approval in the loop

These are short field notes on the queues, documents, drafts, and receipts each agent produces.

TriageDesk


	TriageDesk reads a shared support inbox overnight, classifies each message, and drafts one reply per thread. It is for teams working from Microsoft 365 or Gmail who want a morning queue instead of a wall of unread mail. The queue shows the source message beside the draft, with options to approve, edit, or kill it. Complaints, legal threats, and cancellations go to a human undrafted, while approved replies sit for 120 seconds before dispatch.

TriageDesk reads a shared support inbox overnight, classifies each message, and drafts one reply per thread. It is for teams working from Microsoft 365 or Gmail who want a morning queue instead of a wall of unread mail. The queue shows the source message beside the draft, with options to approve, edit, or kill it. Complaints, legal threats, and cancellations go to a human undrafted, while approved replies sit for 120 seconds before dispatch.

MatchRail


	MatchRail runs a three-way match across bills, purchase orders, and receipts for a month-end close. It is for bookkeepers who need to see what disagrees before a payment run. Each disputed row shows the documents and the reason, such as a missing purchase order or a second copy of an invoice. An approved correction waits 60 seconds, writes an audit row, and re-reads the documents before writing to the ledger.

MatchRail runs a three-way match across bills, purchase orders, and receipts for a month-end close. It is for bookkeepers who need to see what disagrees before a payment run. Each disputed row shows the documents and the reason, such as a missing purchase order or a second copy of an invoice. An approved correction waits 60 seconds, writes an audit row, and re-reads the documents before writing to the ledger.

LeadGrade


	LeadGrade scores every inbound lead overnight and ranks the queue highest-first. It is for sales teams using HubSpot who need the score and its reason beside each lead. Every lead starts at 20 and can add points from form intent, role, company size, email domain, industry, buying language, and completed fields. Approve holds the HubSpot write for 60 seconds, while Kill writes nothing.

CardChase


	CardChase recovers failed subscription charges by reading decline codes, staging retries on a ladder, and stopping hard declines. It is for subscription businesses that need a queue sorted by recurring charge at risk. Each row carries the decline code, issuer advice, attempts spent, and the next rung. A retry can be approved into a 30-second kill window, while a hard decline or a charge at its four-retry cap is stopped.

CardChase recovers failed subscription charges by reading decline codes, staging retries on a ladder, and stopping hard declines. It is for subscription businesses that need a queue sorted by recurring charge at risk. Each row carries the decline code, issuer advice, attempts spent, and the next rung. A retry can be approved into a 30-second kill window, while a hard decline or a charge at its four-retry cap is stopped.

One issue a week, and one shipped product taken apart every month. What each product does, what it cost to build, what the pipeline behind it looks like, and what the numbers did, read off the repository and the live site, not written from memory. Join the list.

CiteRank tracks whether answer engines cite your site

kyisaiah47 — Sun, 27 Sep 2026 20:13:10 +0000

citerank.thecompound.tech

CiteRank's commit 9435a68 fixed a layout defect in src/app/globals.css: prose width rules were leaving dead space beside the console rail. The fix removed those limits so content could fill its column.

CiteRank

The board

The board shows one row per buyer question and one column per answer engine. Each result distinguishes cited, named, and absent.

The board tracks whether an engine links your domain, names your brand without a link, or leaves you out. Its status line shows the last recorded answer date.

Free check

The Free check view presents a question field and a check control for a single prompt. It gives the console a direct way to inspect one answer before tracking it.

The control runs a one-off check and reports whether the answer cites, names, or omits the supplied site. CiteRank keeps that result separate from its weekly board.

llms.txt

The llms.txt view explains the file format and shows the content that can be provided to answer engines. The page presents the document as a readable text artifact.

The view helps inspect whether a site has a clear machine-readable description. It keeps the document itself visible instead of reducing the check to a score.

AEO tools

The AEO tools view presents structured tables for improving how a site appears in answer-engine results. Its controls organize the work around questions, sources, and answer visibility.

The page turns a missing citation into a concrete research task by showing the answer context around the result. It keeps cited, named, and absent states distinct.

How to rank

The How to rank view contains guidance for improving visibility in ChatGPT and related answer engines. Its sections explain how the board's result states differ.

The page connects a result to the source material an engine used. It makes the cited-source list part of the workflow instead of treating visibility as a single number.

The width fix

The defect lived in three selectors that applied the reading measure to content that already had a console column.

- .doc > section > p.doc > section > ul,
- .doc > section > ol.doc > section > h3 {
-   max-width: var(--measure);
- }
+ .doc > section > p.doc > section > ul,
+ .doc > section > ol.doc > section > h3 { }

The same change removed the measure from band headers and ledger captions. I kept the full-width rule for tables because those artifacts use the whole column.

CertScope determines which CPSC rules apply to a SKU

kyisaiah47 — Sat, 26 Sep 2026 20:07:31 +0000

certscope.thecompound.tech

CertScope starts with a product description, an HTS code, and an age group. It turns that input into a rule decision, a certificate draft, and a list of fields that still need evidence.

CertScope

SKU determination form

The main page opens with a determination form containing a product description, an HTS code field, and age-group controls for children's, general, or unknown products.

The Determine control sends those values to the scope service. CertScope returns a certificate type, matched rules, testing requirements, and the rules that need to be cited.

Determination stages

The determination view shows a vertical stage list beside the form. Each stage can display its measured runtime, including values below one millisecond.

The stages move from pending to completed while CertScope runs the determination. The result stays in the same workspace, so the rule register and certificate update from the submitted SKU.

Rule register

The rule register shows the CPSC dataset as separate rows. Each row can be opened to show its rule identifier, name, applicability state, and the basis for that state.

The filter control narrows the register to all rules, applicable rules, or rules that need screening. CertScope moves rows into their new groups when a determination changes.

Certificate sheet

The certificate sheet shows the document produced from the determination. Its sections include the certificate type, cited rules, required information, and the importer details that are still needed.

CertScope writes each applicable rule on its own citation line. Fields that only the importer can provide appear with a required marker instead of being filled with an assumption.

Certificate linter

The linter control replaces the determination form with a certificate text area and a lint action. Its result view lists the seven certificate elements as separate checks.

CertScope marks each element as present or missing and places those marks back onto the corresponding certificate sections. A missing lab result remains visible as missing evidence rather than becoming a passing check.

CardChase recovers failed subscription charges before churn

kyisaiah47 — Wed, 23 Sep 2026 12:10:45 +0000

cardchase.thecompound.tech

CardChase had a real failure mode in commit 04e6130: an admin lookup error could look like "no demo account," allowing a fabricated retry to continue toward payment or email. The fix touched three paths and made the lookup fail closed.

CardChase

The queue

The queue shows seven open charges, their monthly risk, the retry cap, the kill window, and three actions waiting for approval. Each row carries the customer, amount, decline reason, and current rung.

The queue lets me approve, edit, or stop the next retry. Approval stages both the card retry and the customer note behind a 30-second window.

The record

The record shows receipts for failed charges, drafted notes, staged retries, blocked attempts, capped retries, and recovered charges. Each receipt includes evidence such as the invoice, decline code, rung, or stop authority.

The record preserves why CardChase acted or stopped. A permanent decline writes its own receipt instead of appearing as an ordinary retry.

The ladder

The ladder shows four rungs across seven days: a silent retry after one day, then notices after three, five, and seven days. The schedule counts from the first failure, not from the previous attempt.

The ladder decides when a charge becomes due. Before staging anything, CardChase checks the issuer advice, hard-decline codes, and raw network response.

The kill window

The kill-window view shows the 30-second release period shared by the retry and the customer note. An approved action is staged, not sent immediately.

The window lets me undo the action before either side reaches the payment or mail rail. The dispatcher cannot claim the row until the release instant.

How it works

The workflow moves through five named states: failed charge, ladder, gate, approval window, and receipt. The gate can stop the charge before the ladder produces a retry.

flowchart LR
  A[Failed charge] --> B[Ladder]
  B --> C[Stop gate]
  C --> D[Approval window]
  D --> E[Receipt]

The page explains the same path in the console's own terms. CardChase reads the failed charge, checks whether the next rung is due, stages the action, and records the evidence.

The changelog

The changelog shows four shipped changes, including the hard-decline stop, the retry cap, the shared kill window, and direct billing reads. The kill-window entry says approval stages both halves of the action.

Commit 04e6130cf4ba2666c4b8ae559f40c8c99ababd0e fixed the lookup defect in src/app/_lib/dispatch-run.ts, src/app/_lib/pass-run.ts, and src/app/auth/callback/route.ts.

diff --git a/src/app/_lib/dispatch-run.ts b/src/app/_lib/dispatch-run.ts
@@
-  const { data } = adminSupabase().auth.admin.listUsers({ page: 1, perPage: 200 });
+  const { data, error } = adminSupabase().auth.admin.listUsers({ page: 1, perPage: 200 });
+  // A broken admin lookup is not evidence that the demo user is absent.
+  if (error) throw new Error(`Unable to resolve the demo account: ${error.message}`);

I changed the lookup so an error stops the pass before it can reach a real payment or mail rail.

BreachProbe scans a shipped app for database exposure

kyisaiah47 — Tue, 22 Sep 2026 11:48:42 +0000

breachprobe.thecompound.tech

BreachProbe scans a shipped app's JavaScript, response headers, Supabase REST responses, and signed-in behavior, then shows what the app actually serves instead of stopping at a bundle search.

BreachProbe

The scan console

The main console shows one URL field, an authorization checkbox, and a "Scan free" control. It also keeps "NO ACCOUNT · NOTHING INSTALLED · READ-ONLY · ONE URL" beside the control.

The console sends the pasted address through the scan flow. It fetches the shipped page, reads its scripts, checks headers, probes database endpoints, and runs signed-in checks when the app supports them.

The severity filter

The report rail shows Everything, Critical, High, Medium, and Low filters. The worked report marks one critical finding, two high findings, three medium findings, and two low findings.

The filter changes which findings remain in the report river. BreachProbe keeps each finding's title, severity, evidence source, and written fix attached to the same result.

The run order

The console lists the scan in order: shipped JavaScript, exposed API keys, Supabase REST endpoints, security headers, broken-auth patterns, Stripe routes, and two signed-in users.

That order separates passive inspection from behavior tests. The scan reads code and headers first, then checks whether tables answer anonymous requests and whether one signed-in user can read another user's rows.

The sample report

The sample report shows a failing worked example with a critical row-level security finding. It identifies three affected tables and says the read crossed two signed-in users.

The report turns that result into a written SQL fix. It tells the reader to compare auth.uid() with the row owner column and to verify that a fresh user reads zero rows after the policy changes.

The method page

The method page explains what each probe sends and what answer counts as proof. It separates shipped-code patterns, response headers, Supabase REST reads, signed-in isolation checks, and Stripe route checks.

The JWT signing-secret check uses a different standard from a string match. BreachProbe recomputes the HS256 signature of the app's own public key, so a random 40-character build value does not become a finding.

The scan error state

The console keeps the four operating terms visible when a scan fails, then places the error on its own row underneath. The failed state no longer replaces the read-only and no-account explanation.

I changed ScanBar so the assurance text stays mounted independently of the error message. I also added the JWT signing-secret check to the deploy checks after the first implementation swallowed an ES module require error and reported a clean result for every fixture.

Four filings that leave a record

kyisaiah47 — Sat, 19 Sep 2026 13:40:30 +0000

Four filings, each ending in a document someone can use.

What this issue carries

These products turn rule-heavy work into certificates, workpapers, binders, and policy documents.

Product	For	What you get
CertScope	Product importers and brokers	A CPSC rule determination and certificate
Truing	Payroll teams	A workpaper for W-2 box 12 codes TT and TP
DoseTrace	Independent pharmacies	A dated DSCSA readiness binder
QuorumFile	Public housing agencies	A redlined policy chapter and adoption paperwork

CertScope


	CertScope settles which CPSC rules apply to each imported SKU, then builds the certificate a broker needs to clear it. Importers get a determination wizard, certificate linter, and CPC or GCC output, with the rule list shown against the product description.

certscope.thecompound.tech

Truing


	Truing reads one payroll register row per employee per pay period, reconstructs 2026 W-2 box 12 codes TT and TP, and shows which employees cannot be classified. Payroll teams get a workpaper with the overtime premium separated from straight time.

truing.thecompound.tech

DoseTrace


	DoseTrace prepares a DSCSA readiness binder for an independent pharmacy, including the exemption determination, trading-partner log, procedures, tracing runbook, training attestation, and retention plan. The pharmacy owner gets dated documents prepared around the pharmacy's own licence, wholesalers, staff, and headcount.

dosetrace.thecompound.tech

QuorumFile


	QuorumFile helps a public housing agency record its HOTMA elections and produce the policy paperwork for adoption. The agency gets a redlined ACOP or HCV Administrative Plan chapter, a decision sheet, and the board and public-hearing documents that prove the policy was adopted properly.

quorumfile.thecompound.tech

Multiple shipped products, taken apart, few times a week. What each one does, what it cost to build, what the pipeline behind it looks like, and what the numbers did, read off the repository and the live site, not written from memory. Join the list.

BlockDex searches public shadcn registries at the item level

kyisaiah47 — Fri, 18 Sep 2026 13:19:55 +0000

BlockDex puts the install command beside the component it found. That matters when the cost of a bad search is opening registry after registry just to recover a URL.

BlockDex

The console

The console opens with a query for "marquee" and shows matching items in relevance order. Each row carries its type, access result, file count, dependencies, preview state, and an Open the record control.

The page gives the search result enough context to decide whether to inspect it. The install command stays visible, and the row points back to the registry's own item endpoint.

The query desk

The query desk combines a search field with filters for kind, access, page capture, and order. The live controls show counts for components, blocks, hooks, themes, utilities, free results, paid results, unverified results, live frames, and captures.

Each chip opens a stored view of the same index. The active filter is named in the compact control, so opening a filtered view does not hide which slice is on.

The registry shelf

The registries page shows a shelf of sources with item totals, GitHub facts, licence text, access results, and crawl state. The page separates registries that answered from registries that stopped answering.

The shelf uses consecutive silence before removing a source from the active view. A registry that fails once stays distinguishable from one that has stopped answering.

View	What it shows	What it answers
Every registry	997 sources	Which registries serve a parsing manifest
Free	462 sources	Which item endpoints answered without a key
Free plus paid	12 sources	Which sources returned mixed access results
Unverified	518 sources	Which sources expose no item endpoint to ask

The method page

The method page lays out how BlockDex finds registries, decides whether a manifest counts, probes access, checks previews, and handles missing sources. It also states what the index refuses to measure, including quality scores and registry rankings.

The page ties each figure to something a registry served. It keeps the crawl method beside the result instead of asking the reader to treat a directory label as evidence.

The item record

An item record shows the namespaced id, type, files, first-seen date, last-seen date, registry, stars, preview state, dependencies, and the registry's own documentation address. The page also prints the install command and identifies whether the source came back.

The record lets a builder inspect one result without losing the provenance around it. The install path resolves to the registry's endpoint, while BlockDex keeps the item metadata and access reading beside it.

The API reference

The API reference lists the search, item, registry, statistics, health, and registry-resolution endpoints. It shows the accepted parameters, response purpose, cache notes, and example calls.

The page also shows how to add the BlockDex namespace to a components configuration and search it from the shadcn CLI. A namespaced item resolves to the source registry rather than serving a copied component from BlockDex.

BenchFile checks a building, clears an open Local Law 84 violation, and files each year

kyisaiah47 — Thu, 17 Sep 2026 12:46:57 +0000

Open BenchFile

BenchFile checks a New York City building address against Local Law 84, shows whether the city has issued an open benchmarking violation, and lays out the filing work in the same console.

BenchFile

Building lookup

The main page starts with one address field and a live building result. It shows the building name, owner, borough, square footage, units, and a link to the building's public record.

The lookup sends the address to NYC Open Data and checks the city's benchmarking violation and PLUTO datasets. BenchFile keeps the typed lookup out of its own database.

Open notices

The middle column shows the building's open notices as a ledger. Each row carries a violation number and issue date, with the current penalty state beside it.

Selecting a notice opens its details and loads the payment path for that specific violation. The console also shows the quarterly penalty and the amount accrued against the building.

View	What it shows	What it does
Building lookup	Address, owner, borough, square footage, and units	Checks public building data
Open notices	Violation number, issue date, and penalty state	Opens a notice-specific record
Payment kit	Filing documents for the selected notice	Shows what the engagement produces
Pricing	One-time and annual service tiers	Separates curing from ongoing filing

The table reflects the four views visible in the BenchFile console. The building lookup and notice ledger are driven by public city data, while the payment kit and pricing views describe the service path.

Payment kit

The right column shows a sample payment kit with a document preview, title, and table of contents. When a notice is selected, the panel switches from the sample to a kit drawn for that violation.

The same generator writes the PDF and the console preview. The page names the violation number and building address so the document is tied to the record being reviewed.

Pricing

The pricing page shows two separate cards. "Clear the violation" costs $149 once and then $49 per year, while "Stay compliant" costs $49 per year for a covered building with nothing outstanding.

The first tier files the overdue report and keeps the building filed before the May 1 deadline. The second tier covers the yearly report without a one-time cure because there is no open violation to clear.

Questions

The Questions page presents BenchFile's answers from its own question register. It covers the Local Law 84 deadline, the $500 quarterly penalty, the 30-day challenge window, and the difference between benchmarking and the energy-grade label.

The answers also describe the cases where BenchFile challenges a notice instead of curing it, including a building that is not covered, was benchmarked on time, or was demolished.

Security

The Security page states that BenchFile has no user accounts, passwords, or sign-in sessions. It also explains that an address lookup is sent to NYC Open Data and is not written into BenchFile's database.

The page names the processors for payments, analytics, hosting, and public-data lookups. Stripe hosts the checkout, so a card number is never typed into the BenchFile site.

Open BenchFile

Four directories with different jobs

kyisaiah47 — Tue, 15 Sep 2026 16:28:30 +0000

These four directories collect and explain software for people who need to choose what gets installed, submitted, or trusted. Each one turns a scattered source into a page with a clear answer.

What they cover

This issue carries short descriptions of four directories that make software easier to inspect and use.

StoreReady


	StoreReady compares AI and no-code mobile builders against App Store submission requirements. It is for developers choosing a builder and gives them sourced verdicts about output, developer accounts, submission paths, and review caveats.

storeready.thecompound.tech

Agentwire


	Agentwire is a curated wire of MCP servers, coding-agent harnesses, and agent frameworks that other developers have shipped. It is for people looking for agent tooling and gives them dated entries with source checks, categories, and descriptions of what each tool does.

agentwire.thecompound.tech

BlockDex


	BlockDex searches shadcn registries item by item and records whether each component, block, hook, theme, utility, or example is free, paid, verified, or previewable. It is for React developers who need registry items they can inspect before installing.

blockdex.thecompound.tech

Four wires carrying source stories into readable pages

kyisaiah47 — Tue, 15 Sep 2026 15:48:23 +0000

This issue follows four wires that turn source material into something you can read and act on. Each one puts a different kind of live information into a clear page, archive, or email.

What this issue covers

These products collect current stories, name their sources, and give readers a usable record.

Front Wire


	Front Wire brings earthquakes, severe-weather alerts, SEC filings, and world headlines into one live feed. It is for readers who want agency, filing, and outlet links beside each item, plus an archive and a daily email.

frontwire.thecompound.tech

Popwire


	Popwire is a visual news wire that shows one story with its headline, summary, reporting outlets, category, and source links. It is for readers who want to browse the feed, search outlet names, and open each story's full record.

popwire.thecompound.tech

The Standup


	The Standup tracks releases, CVEs, outages, and breaking changes across the vendors and repositories you depend on. Developers get a daily wire, an action-focused board, and an email ordered around what needs attention.

standup.thecompound.tech

KitGrade, RuleStack and SkillWorks

kyisaiah47 — Sun, 13 Sep 2026 00:49:03 +0000

This issue brings together products that turn public software into information people can check before choosing what to use. Each one gives builders a directory, score, comparison, or source-backed result instead of an unsupported recommendation.

What this issue covers

These pages help builders inspect starter kits and agent instructions before they install or adopt them.

KitGrade


	KitGrade scores SaaS starter kits from public commits, shipped code, pricing pages, and documentation. A founder choosing a stack gets ranked kits, scores, prices, licences, stack details, measurement coverage, and install transcripts where the kit was run.

kitgrade.thecompound.tech

RuleStack


	RuleStack counts AGENTS.md, CLAUDE.md, Cursor, Copilot, Cline, GEMINI.md, Windsurf, and related instruction files from live repositories. Developers get searchable files, stack classifications, quality scores, freshness data, format comparisons, and an API backed by the nightly corpus.

rulestack.thecompound.tech

SkillWorks


	SkillWorks scores Claude Code skills, subagents, plugins, and marketplaces from their source files. Developers get checks for parsing, required fields, referenced files, maintenance, adoption, documentation, and the exact reason a listing will not load.

skillworks.thecompound.tech