But that means our model is only ever going to grow into our vision of it. How myopic of a vision is that? We can't let that happen. We need people that spot more exact pairings between what we can provide and interesting problems that need solved.

Partners keep us on the edge of a very important intersection: what we choose to pursue, and how that pursuit can help people add value to their lives and businesses.

We want a constant stream of people trying to hammer our research into corners that we never thought it would go, or even existed. And you know what? We're pretty good friends to have!

Structurally Uncommon

Let's make sure we're clear up-front because our structure might suggest otherwise: we are capitalists. We intend to build a highly sustainable, profitable engine. But how we use that money, and why we are in this game, is drastically different than the standard venture-backed playbook.

Our organizational structure is coalescing around a model that hasn't quite been tried before; one designed specifically to prevent the institutional decay that eventually forces platforms to betray their users by 'firing' the vision that blocked them.

We are still finalizing the exact corporate registration details to ensure the legal mold perfectly fits our actual growth, but the core tenet is already locked in: our partners are never treated as mere vendors or extractive revenue streams, not even on a constitutional level.

We are changing the rules of the game so we can win on our own terms, and we are looking for like-minded people who want to build in that same reality.

What Partners Receive

• Access to our engineers through Slack/Discord (not standard public channels)

• Hosting on our infrastructure, as-appropriate

• Co-marketing and Co-branding opportunities

• Participation roles in research

• Respect, admiration and appreciation

• Personalized, detailed responses with our decision, criteria and information considered, reasons for the decision and next steps (including appeal if appropriate). We don't automate it.

What Partners Never Receive

• Non-disclosure or non-compete agreements. If you spill your own beans, it's on you; don't let us stop you. We only publish collaboratively with you.

• Surprises. Each initiative has its own terms, agreed in advance. If you show up, we'll show up. We don't have "Developer program terms" because this isn't a mass-product, it's a relationship we intend to participate personally in.

What Partners Need To Show

• An appropriate need for our products. The problem type has to fit. Magnets won't attract wood, for instance, so there's little point in pretending it might work unless you're bringing something new.

• A willingness to be wrong as well as brilliant. Many iterations fail for many reasons, some turn out to be premise-shattering. This isn't the first ever application of this technique, but it's the first attempt at a defined interface for it.

• A potential for growth. There has to be a business gain in here, somewhere. We look ato many factors when it comes to potential, including how it could add to other projects.

How To Propose Collaboration

We need to know some base information about how you envision us adding value to reaching your goals. Fill out this short survey and someone from Engineering or our Business execution team will look at your application.

Your application is first evaluated by our business end to make sure there's currently room and resources to support you. It's dynamic, based on our bandwidth and number of engineers actively contributing on a set schedule.

Many applications will be a great fit at the wrong time, but that doesn't always mean it will be politely declined. We may be able to offer you infrastructure and some code, or a variation of what you propose. We'll work to say yes.

And if we can't, we'll politely decline for now, and honestly keep in touch with the goal of trying again when circumstances better align.

There Are Ground Rules

1. You can't violate or conspire to violate US law with our products or services, obviously.

2. Your use must withstand ethical scrutiny if we're involved without technical rules-lawyering. This is non-negotiable. We do not discriminate against fields of endeavor but we do draw a line at harm.

3. We have a code of conduct that relates to how we interact together. We bring one, but we mostly just care that we use one and work from a few agreed-upon expectations in how we interact.

4. Deference isn't automatic; respect is a phenomenological variable. We invest our attention in actions and outcomes; in our own as well as others. We respect the body of work that credentials and certifications represent, but on missions, it's what you've done that gets the microphone the most because it's what we can actually use.

If you're a good fit for this program, the above bullets should feel more like assurances than obstacles. If that's the case, reach out to us!

I'm pleased to announce that I shared Aldous' launch announcement:

The article below introduces Aldous, a zero-shot semantic telemetry engine built to do exactly that. It operates on Diagonal Emotional Covariance Estimation (DECE), calculating the centroid and dimensional variance of concepts in latent space to output distance and similarity floats in constant time.

There is no string matching and no generative reasoning, just open observability. If you are working on the math or governance side of AI, I encourage you to read the architecture breakdown. My approach isn't exactly new, but it is pretty novel, if I do say so myself because it's #Semantic, boogie woogie, woogie!

Please consider dropping the open-source variance harness into your own CI server to establish your own content baselines, and please subscribe to my new newsletter that tracks the journey of this ongoing, rewarding, and often beguiling research. I won't publish an installment unless there's plenty to say.

I really suggest that you also check out the article that I mention.