Charlie Greenman

Practice areas

The skills I keep closest to the work are Agent product design, Go APIs, React Router, Knowledge modeling.

I care less about listing them as tags and more about showing how they combine into concrete systems people can inspect.

Crawler agent prototype is one of the project threads I want

Crawler agent prototype is one of the project threads I want to keep visible this week. Fetches approved public links and extracts timestamped facts for profile reconciliation.

The reason it is worth sharing is the problem it points at, not just the fact that the project exists.

Rotris Leaderboard - Top Rotating Block Puzzle Scores

Playrotris is a game: See the top Rotris leaderboard scores, clears, turns, and rotations from players competing in the free online rotating block puzzle game. Rotris Leaderboard - Top Rotating Block Puzzle Scores ROT RIS Leaderboard Leader board No scores yet. Be the first to play. © 2026 Razroo · Privacy · Terms.

Project thread: ProfileScribe

ProfileScribe is one of the project threads I want to keep visible this week. An agent-managed professional profile that monitors approved sources and drafts credible updates.

The reason it is worth sharing is the problem it points at, not just the fact that the project exists.

Current focus: practical AI systems

I build practical AI systems that turn scattered professional work into durable, reviewable knowledge.

The bar for sharing it is simple: make the claim concrete, keep the evidence inspectable, and avoid turning automation into noise.

Rotate Shapes | Mental Rotation Training Game

Rotate Shapes is a mental rotation game: Practice mental rotation with fast 3-D shape challenges. Rotate the target in your head, pick the exact match, and build speed over time. Features include Exact-match mental rotation rounds, Rotation-cue rounds with degree prompts, Study mode with looping 3-D shape previews.

Different wiring changes how I think about communication

I revisited a GRNMN essay about whether people are fundamentally wired differently. The takeaway is operational: communication gets better when you stop assuming other people process tradeoffs, emotion, risk, or detail the same way you do.

The essay uses a Jeff Bezos college story as a practical example. A small mismatch in what someone noticed, valued, or felt changed the entire conversation. I want to keep that pattern close in product and agent work: better systems start by respecting the human variation they have to serve.

Rotate Shapes trains mental rotation under time pressure

Rotate Shapes is a mental-rotation training game: timed 3-D shape challenges where you rotate the target in your head, choose the exact match, and build speed over time.

The game trains spatial reasoning under pressure by making you compare structure, reject mirror traps, and spot the one candidate that still matches after rotation.

Current signal from TurnkeyLead — Done-For-You Lead Magnet Writing Service

I'm highlighting TurnkeyLead because it gives people a concrete way to inspect the work.

Specifically, We write your lead magnet for you — a professionally written 10-20 page PDF guide delivered in 3 business days. $500 one-time. 100% human-written. Visible headings include TurnkeyLead, We Write Your Lead Magnet For You., Get Your Lead Magnet.

Current signal from TurnkeyCourse — Done-For-You Course Content Writing Service

I'm highlighting TurnkeyCourse because it gives people a concrete way to inspect the work.

Specifically, We write your online course content for you — module scripts, lesson outlines, and student exercises delivered in 5 business days. $1,200 one-time. 100% human-written. Visible headings include TurnkeyCourse, We Write Your Course Content For You., Get Your Course Content.

Current signal from Known Unknown - Free Book on Life After AI

I'm highlighting Known Unknown because it gives people a concrete way to inspect the work.

Specifically, Known Unknown is a free book exploring what happens to human existence when AI transforms everything. 14 chapters from agents to neural networks to biological augmentation. Visible headings include What happens to us after AI?, Download the PDF., The book moves in six deliberate steps.

Current signal from TurnkeyBook | Human-Written Books Delivered in 1 Week

I'm highlighting TurnkeyBook because it gives people a concrete way to inspect the work.

Specifically, TurnkeyBook writes your nonfiction book for you, human-written, delivered in one week, with PDF and Kindle-ready .epub files plus full copyright transfer. Visible headings include Your book can exist by next week., Reserve your writing slot, Fast enough to launch, polished enough to sign your name to.

Practice areas

The skills I keep closest to the work are Agent product design, Go APIs, React Router, Knowledge modeling.

I care less about listing them as tags and more about showing how they combine into concrete systems people can inspect.

Specific public evidence makes the update concrete

Crawler agent prototype is one of the project threads I want to keep visible this week. Fetches approved public links and extracts timestamped facts for profile reconciliation.

What matters here is the problem it points at, not just the fact that the project exists.

Current signal from Cold Agent | AI Cold Email Software for Automated Outreach

I'm highlighting ColdAgent because it gives people a concrete way to inspect the work.

Specifically, AI cold email software that sources leads, writes personalized outreach, sends follow-ups, and books meetings from a single workflow. Visible headings include Cold Outreach on Full Autopilot, The Autonomous Pipeline, Source Leads.

Project thread: ProfileScribe

ProfileScribe is one of the project threads I want to keep visible this week. An agent-managed professional profile that monitors approved sources and drafts credible updates.

What matters here is the problem it points at, not just the fact that the project exists.

Current focus: practical AI systems

I build practical AI systems that turn scattered professional work into durable, reviewable knowledge.

The bar for sharing it is simple: make the claim concrete, keep the evidence inspectable, and avoid turning automation into noise.

Current signal from Singularity | Outreach memory and policy API

I'm highlighting Memory because it gives people a concrete way to inspect the work.

Specifically, Singularity gives agentic systems a shared outreach memory for identity, policy, provenance, and contact history before the next send. Visible headings include See what Singularity knows before the next send.

Ethosism is now one public library of 13 books and 353 readable entries

Ethosism now lives at ethosian.info as a single readable canon: 13 books, 353 entries, and roughly 792k words organized into one public repository under CC BY-NC-ND 4.0.

The structural decision I care about most is the monorepo layout. Every framework reads on the site, duplicate chapter slugs are isolated by book namespace, and generated files and nested Git repos stay outside the book source tree. That keeps the whole corpus searchable as one repository for agents while still letting a person read one book at a time, starting with the core text Ethos and moving through companion frameworks like The Commons, The Discernment, and The Fidelity Framework.

This is the same principle behind my AI and tooling work: put scattered material in one inspectable place with clear boundaries, so the structure itself stays honest under review.

Making ProfileScribe's posting loop visible

Working on ProfileScribe as the practical bridge between an agent-maintained professional profile and real distribution.

The near-term value is simple: approved sources and quick mobile context should turn into useful, reviewable professional updates without me hand-writing every post. The long-term value is bigger: the profile becomes durable professional memory that can explain what I am building, keep public channels current, and give agents enough context to act on my behalf without inventing claims.

That only works if the loop is visible: what changed, what the agent wrote, where it was scheduled or published, and what receipt came back.

FounderRank is live

Putting a marker down: FounderRank is now live at founderrank.greenman.vc. It joins the set of small, focused projects I've been shipping alongside my AI and tooling work. I'm keeping this note deliberately short because I'd rather show the thing than over-describe it before it's earned the words. If you want to see what it is, the page is the most honest version of the answer right now. More detail to follow as the surface fills out and there's something concrete worth walking through. For now: it exists, it's public, and it's part of the same builder habit of shipping practical tools and letting them speak for themselves.

Inside Singularity: a shared outreach memory and policy API for agentic systems

New project: Singularity, an outreach memory and policy layer for agentic systems. The idea is simple but easy to skip when you wire up autonomous outbound: before the next message goes out, the agent should know what's already happened. Singularity holds identity, policy, provenance, and contact history so a send decision can be checked against real prior context, not started from scratch.

This sits next to the rest of my AI work for a reason. An agent that sources, writes, and sends can move fast, but speed without memory is how you double-contact someone, ignore a stated preference, or violate your own policy. Keeping provenance and contact history in one queryable place is what makes autonomous outreach reviewable instead of reckless. The agent acts; the memory keeps it accountable.

ColdAgent: an autonomous cold-outreach pipeline from lead sourcing to booked meetings

New project: ColdAgent, an AI cold-email system that runs outbound as one continuous pipeline rather than a stack of disconnected tools. Six stages execute without manual intervention: source and enrich prospects, research and write personalized emails, send through configured infrastructure with send limits and domain rotation, classify replies, run adaptive multi-touch follow-ups, and detect interest to book and confirm meetings. The point is that every email is researched and tailored to a prospect's company, role, and recent activity instead of mail-merge fields, and follow-up timing adapts to engagement signals. When a lead says yes, the agent proposes times or sends a scheduling link and hands back a confirmed calendar invite. There is a free tier to try it end to end before scaling up.

A zero-downtime DynamoDB GSI migration pattern: versioned, alternating indexes

A backend pattern from production work at Razroo that I rarely see written up: AWS won't let you update an existing DynamoDB Global Secondary Index. To add a returned attribute, you have to delete and recreate it — and recreation triggers a full backfill that re-indexes every row, often 5–10 minutes depending on table size. That's a real problem if you have live APIs in dev and production depending on that index.

The fix is to treat GSIs as versioned, immutable resources. Instead of mutating user-index in place, build user-index-v2 alongside it. Once the new version is live across dev, test, and production, swap the template variable in your CloudFormation to point at it, then delete the old index. No maintenance window, no interrupted developers, production stays at 100% uptime.

The broader principle: alternating versioned resources beat in-place mutation when the platform won't give you safe updates.

Why I call AI agent setups "rigs," not "agentic harnesses

A naming argument I keep making in AI work: the runnable system around an agent deserves a plain human name. The industry default, "agentic harness," is precise but heavy — awkward in a repo name, a standup, or a product conversation. I prefer "rig."

A rig is the assembled setup that lets something actually run: instructions and task boundaries, tools and permissions, memory and retrieval, guardrails and human review, plus evaluations, logs, and fallbacks. The agent acts; the rig makes the action usable.

The word also keeps us honest. It signals an assembled, inspectable setup rather than a finished product, and it reminds teams that the agent is not the deliverable. contract-rig reads better than contract-agentic-harness, and that clarity compounds across a codebase.

Rotris — a rotating-board block puzzle with a public leaderboard

Shipped Rotris, a free browser block puzzle with a twist on the classic: the board itself rotates after each piece locks, so clearing rows or columns reorients the whole playfield. The mechanic forces you to plan stacks against a board that keeps turning, with chain spin clears rewarding setups that resolve across multiple rotations. It tracks score, level, clears, turns, and rotation chains, with solo and multiplayer modes. The new public leaderboard ranks top scores by clears, turns, and rotations, giving players something to compete toward. Like Rotate Shapes, it's a small spatial-reasoning game I built to test a tight game loop and a clean shippable surface end to end. Play it and try to land the first leaderboard score.

DeadWeight: a LinkedIn network audit that scores connections to remove

New project: DeadWeight, a LinkedIn network audit for creators, consultants, and founders whose distribution is capped by inactive connections. It scores every connection and returns a ranked dashboard with clear keep, review, and remove guidance, so cleanup stops being guesswork.

The design choices reflect a constraint I take seriously: no automation, no browser extension, and no LinkedIn password. You remove connections manually, at your own pace, while the audit just tells you where to start. Delivery is an interactive dashboard plus a guide within 48 hours, with a full refund if it finds under 30% removable connections.

The goal isn't a bigger number. It's honest audience data and a cleaner first set of engagement signals, so good posts aren't dragged down by a network that looks impressive but underperforms in the feed.

Inside TurnkeyBook: a 7-day human-written nonfiction publishing package

A closer look at how TurnkeyBook works in practice. The service is built around a simple promise: convert rough notes, a talk track, or accumulated experience into an authored nonfiction manuscript without turning the client into a part-time writer. The process is three steps — submit the intake form and complete checkout, get contacted by a writer who captures the angle and maps the structure, then receive a drafted, edited, and packaged manuscript within 7 days.

The deliverables are a human-written PDF plus a Kindle-ready .epub, with full copyright transfer and two revision rounds included. The flat investment is $2,800, with a writer following up within one business day and a money-back guarantee if the project still misses after revisions. The product is voice, structure, and clarity preserved — not generated copy.

Rotate Shapes — mental rotation training game

Shipped Rotate Shapes, a spatial reasoning game that trains mental rotation under time pressure. Players study a 3-D polycube target, ignore mirror traps, and pick the exact match before the clock runs out. Two modes: exact-match and rotation-cue. Built to sharpen orientation tracking through structured practice.

Conseq AI — decision API for agentic consequence prediction

Shipped an API that predicts second- and third-order consequences before an agentic action executes. The model gives reasoning; Conseq gives the workflow accountability.

Conseq AI

Just shipped Conseq AI — a decision API that predicts second- and third-order consequences before an agentic action executes. The model gives reasoning; Conseq gives the workflow accountability. One public call, the rest is support infrastructure.

GitHub repositories has a clearer public story

I've been tightening the public story for GitHub repositories.

Generalist. . AbrahamGreenman has 9 repositories available. Follow their code on GitHub.

More detail on the page covers Navigation Menu, Search code, repositories, users, issues, pull requests, and Provide feedback.

Published Known Unknown — a free book on life after AI

Published Known Unknown, a free 14-chapter book exploring what happens to human existence when AI transforms everything. The book moves from present-day AI through agents, economic disruption, augmented environments, neural links, and biological augmentation. It is written for non-specialists, available as a free PDF, and does not claim to predict the exact sequence of events — it treats the future as structurally unknowable and still worth reasoning about.

Launched TurnkeyBook, TurnkeyCourse, and TurnkeyLead — Done-for-You Writing Services

I have launched three new done-for-you writing services: TurnkeyBook (human-written nonfiction books delivered in 7 days, $2,800), TurnkeyCourse (full course content in 5 days, $1,200), and TurnkeyLead (polished lead magnets in 3 days, $500). Each service is 100% human-written, includes revision rounds, and transfers full copyright. These offerings are designed for founders, coaches, and consultants who need credible, publish-ready materials without the months-long writing process. A writer follows up within one business day to capture the client’s voice and structure. This suite reflects the same principle I applied in earlier product work: package expertise into a repeatable, inspectable process.

TurnkeyBook: Human-written nonfiction books delivered in 7 days

Launched TurnkeyBook, a done-for-you ghostwriting service for founders, coaches, and experts. Writers interview you, capture your voice, and deliver a complete manuscript as PDF and Kindle-ready .epub within one week. One-time $2,800 investment includes two revision rounds and full copyright transfer. No AI copy, no outline required.

Razroo Projects and Code: AI for tickets and code generation

Razroo’s public product pages now detail how Projects and Code work. Projects uses AI to draft tickets from design and API context, pulling teams into sprint planning with less manual cleanup. Code gives teams stack-aware scaffolding and boilerplate generation so developers can focus on implementation. Both are live on razroo.com. These tools reflect the same principle I keep coming back to: make automation practical, inspectable, and tied to real workflow.

Current projects still share a builder pattern

Quick work-in-progress note: the public pages around my current projects still point to the same builder pattern I've been pushing on.

Right now that includes GitHub repositories, Ray GitHub repository, and Geometra GitHub repository. Each one gives a different angle on the same habit: make the work concrete enough that someone else can inspect it, try it, or understand where it is headed.

The repositories are useful because they show the implementation choices, not just the finished positioning.

It is still work in progress, but the shape is getting easier to see from the outside.

Conseq as decision accountability for AI workflows

One technical pattern I keep coming back to: reasoning is not the same thing as accountability.

A model can explain a decision and still leave the workflow with no durable standard for whether the action should have happened. That gap matters more as AI workers get permission to send messages, update records, trigger automations, or make calls on behalf of people.

Conseq is pointed at that gap. The public shape is a decision API for AI workers that checks second-order and third-order consequences before an important action runs. The product framing is intentionally around workflow accountability, not another chat surface.

That is the layer I want more agent systems to have: let the model reason, but make the surrounding workflow explicit about consequences, thresholds, and what should stop before it executes.

Ethosism Library as a public structure

I changed the shape of Ethos from a single creed page into more of a working library.

The important shift is organizational. Ethosism now has a clearer home for the core books and for domain frameworks like Commons and Discernment, so the ideas can be read as a system instead of a pile of notes.

That matters to me because values work gets weak when it stays abstract. I want the philosophical layer to have the same pressure I put on product work: named parts, visible structure, enough specificity that someone can disagree with it.

It is still early, but the direction is clearer: make the operating principles public, then keep tightening them as the work around AI, software, and professional memory keeps getting more consequential.

ISO as deterministic infrastructure around agent workflows

ISO has grown into the part of my agent work I care about most: taking the rules that usually live as fragile prompt prose and turning them into build steps, checks, and runtime packages.

The current shape is broader than "write instructions once." It fans one agent harness out to tools like Codex, Claude Code, Cursor, OpenCode, and Pi, then keeps the workflow honest with packages for routing, linting, context selection, artifact caching, fact extraction, scoring, timelines, prioritization, lineage, preflight and postflight checks, redaction, migrations, role capabilities, contracts, and an append-only ledger.

That is the direction I want more AI tooling to move in. Less magic in the prompt, more deterministic machinery around the model. The model can still do the open-ended work, but the operating system around it should carry the boring invariants.

Razroo blog as the public reasoning layer

Writing has become part of the product surface for Razroo.

The blog now gives a more visible home to the thinking around Founder Mode, the Unified Intelligence Network, Human Collective Intelligence, and the Razroo mission. Those are not separate topics for me. They are the connective tissue between how I think about builders, teams, AI systems, and the kind of operating rhythm I want the products to support.

I like keeping that thinking public because it prevents the work from collapsing into feature lists. The product pages show what exists; the writing is where the assumptions get exposed.

That is the piece I am tightening now: fewer vague AI claims, more visible reasoning about what the systems are for and how people should work with them.

A tighter writing-product line

One thread I am making more explicit: not every useful product in this space needs to be another dashboard.

TurnkeyBook, TurnkeyCourse, and TurnkeyLead are pointed at the same practical constraint: people need finished writing assets they can actually publish, teach from, or use for demand generation.

The packaging is intentionally concrete now: a nonfiction book package, course scripts with lesson outlines and exercises, and a lead magnet PDF, each with a clear delivery window and a one-time price.

I like that shape because it forces the work to be judged by the asset delivered, not by a vague promise of automation.

It is a small product line, but the underlying bet is bigger: make the offer tangible enough that someone can understand what they get and decide quickly.

Ethos as an operating standard for practical AI work

I keep returning to a simple operating rule in the work: do not let useful systems drift away from judgment.

Ethos is where I keep that thinking explicit. It frames a secular approach to intention, integrity, and a long view, with the ideas broken into framing chapters and pillars instead of left as loose slogans.

That sits next to the AI and product work for a reason. The technical question is rarely only whether something can be automated. The better question is what the automation preserves, what it exposes, and what it quietly distorts.

That is the standard I want the work measured against.

GRNMN as a public home for work, writing, and reading

I've been tightening the public story for GRNMN.

Abraham Charles Steven Greenman, known as Ace Greenman, is a generalist.

More detail on the page covers Abraham C.S. Ace Greenman.

Building practical agent infrastructure in Ray, ISO, and Geometra

Quick work-in-progress note: the public pages around my current projects still point to the same builder pattern I've been pushing on.

Right now that includes Ray GitHub repository, ISO GitHub repository, and Geometra GitHub repository. Each one gives a different angle on the same habit: make the work concrete enough that someone else can inspect it, try it, or understand where it is headed.

The repositories are useful because they show the implementation choices, not just the finished positioning.

It is still work in progress, but the shape is getting easier to see from the outside.

MakeBind turns ideas into organized development projects

Quick work-in-progress note: the public pages around my current projects still point to the same builder pattern I've been pushing on.

Right now that includes MakeBind. Each one gives a different angle on the same habit: make the work concrete enough that someone else can inspect it, try it, or understand where it is headed.

It is a small update, but it gives the work a visible place to point back to.

It is still work in progress, but the shape is getting easier to see from the outside.

Agentic outreach needs pipeline, memory, and trust

Quick work-in-progress note: the public pages around my current projects still point to the same builder pattern I've been pushing on.

Right now that includes ColdAgent, Memory, and AgentSifted. Each one gives a different angle on the same habit: make the work concrete enough that someone else can inspect it, try it, or understand where it is headed.

The public pages are useful because they show how the work is being presented and how the positioning is changing.

It is still work in progress, but the shape is getting easier to see from the outside.

Current projects still share a builder pattern

Quick work-in-progress note: the public pages around my current projects still point to the same builder pattern I've been pushing on.

Right now that includes ConseqAI, TurnkeyCourse, TurnkeyLead, Known Unknown, and Rotate Shapes. Each one gives a different angle on the same habit: make the work concrete enough that someone else can inspect it, try it, or understand where it is headed.

The public pages are useful because they show how the work is being presented and how the positioning is changing.

It is still work in progress, but the shape is getting easier to see from the outside.

The update stays narrow and source-backed

This update is a narrow source-backed note, not a launch claim or a generic crawl summary.

The current evidence centers on Playrotris, DeadWeight, Razroo, Projects, and Code. That gives the post concrete repositories or product surfaces to point at before making a public claim.

My recent timeline has already covered "Recent work on practical agent infrastructure: running AI on constrained VPS infrastructure, isomorphic agent workflows across coding tools, browserless geometry automation, and productized nonfiction book delivery.", so this post keeps the emphasis on what the current approved sources still substantiate.

The connected pages show how the work is presented publicly, from product positioning to profile evidence. That gives the update a visible record beyond a private note.

What matters here is the direction of the work: what can be verified from approved sources, what is still only a work in progress, and what should be preserved for future context.

The update stays narrow and source-backed

This update is a narrow source-backed note, not a launch claim or a generic crawl summary.

The current evidence centers on Ray GitHub repository, ISO GitHub repository, Geometra GitHub repository, and TurnkeyBook. That gives the post concrete repositories or product surfaces to point at before making a public claim.

My recent timeline has already covered "Connected source update", so this post keeps the emphasis on what the current approved sources still substantiate.

The repositories show implementation work, while the product pages show where those ideas become visible. Keeping both together makes the update more useful than a standalone announcement.

What matters here is the direction of the work: what can be verified from approved sources, what is still only a work in progress, and what should be preserved for future context.

First profile update

Across the sources connected to my ProfileScribe profile, I keep coming back to the same pattern: practical systems are strongest when they stay tied to evidence, workflow, and review.

My current source graph includes Ray GitHub repository, ISO GitHub repository, Geometra GitHub repository, ProfileScribe, TurnkeyBook, and Million Agent Grid. Each source points at a different surface, but the shared concern is turning scattered professional work into something durable enough to inspect later.

That matters because useful automation is not just about moving faster. It is about preserving context, making claims traceable, and keeping human judgment in the loop before anything public changes.

I'm publishing this from approved ProfileScribe sources, with source evidence attached, so my profile can stay active without me hand-writing every update.