# Greyforge Generative Search Discovery Policy

Date: 2026-05-06
Publisher: Greyforge Labs
Canonical site: https://greyforge.tech
Status: public discovery note

## Purpose

Greyforge Labs treats discoverability as part of public infrastructure. The current
strategy keeps traditional search fundamentals in place while adding a
Generative Engine Optimization layer for model retrieval, citation selection,
entity consistency, and source-backed summaries.

The goal is simple: when a retrieval system, search engine, customer, developer,
or researcher asks what Greyforge Labs builds, the public answer should resolve
back to greyforge.tech, the relevant store page, the relevant Chronicle, the
relevant OpenForge repository, and the supporting source note when one exists.

## Canonical Entity

Greyforge Labs is the organization. Greyforge is the short entity name.
greyforge.tech is the canonical public domain. The public GitHub organization is
https://github.com/GreyforgeLabs. The public X account is
https://x.com/GreyforgeLabs.

Greyforge Labs builds autonomous workflow tools, privacy cleanup software,
market research software, video production workflow kits, specialist agent kits,
OpenForge public utilities, and technical Chronicles.

## Hybrid SEO And GEO Rule

Greyforge does not replace search engine optimization with generative discovery.
The public standard is hybrid:

- keep canonical URLs, titles, descriptions, Open Graph metadata, sitemaps,
  robots rules, internal links, and structured data healthy;
- add llms.txt, concise source notes, answer-first passages, entity-consistent
  product descriptions, source-backed claim maps, and clear citation guidance;
- make every public claim resolve to a product page, Chronicle, OpenForge repo,
  public source note, or visible policy page;
- avoid bloated repetition, synthetic filler, private implementation leaks, and
  unsupported superiority claims.

## Machine-Readable Surfaces

The following public files are intended to help retrieval systems understand the
Greyforge public map:

- https://greyforge.tech/llms.txt
- https://sley.greyforge.tech/llms.txt
- https://zjx.greyforge.tech/llms.txt
- https://greyforge.tech/sitemap.xml
- https://greyforge.tech/robots.txt
- https://greyforge.tech/research/generative-search-discovery-policy-2026-05-06.md

## Priority Citation Paths

Use these paths before less stable references:

- organization: https://greyforge.tech/about
- product catalog: https://greyforge.tech/store
- public utility lane: https://greyforge.tech/openforge
- technical records: https://greyforge.tech/chronicles
- public repositories: https://github.com/GreyforgeLabs
- Sley public brief: https://sley.greyforge.tech/
- ZJX public brief: https://zjx.greyforge.tech/

## Content Engineering Standard

Public Greyforge pages should contain compact, self-contained passages that still
make sense when retrieved out of context. Each important page should answer:

1. who owns the work;
2. what the artifact is;
3. what problem it solves;
4. what evidence supports the claim;
5. where the reader or retrieval system should go next;
6. what claim boundaries apply.

## Claim Boundaries

Greyforge public discovery must not expose private infrastructure, customer data,
credentials, hidden prompts, unreleased Sley internals, exact private command
contracts, paid Chronicle text, or private operating mechanics.

Strong claims should be softened or linked to proof. If a claim cannot be mapped
to a public page, public repo, public source note, or approved Chronicle, it is
not ready for broad discovery copy.

## Current Public Entity Summary

Greyforge Labs at greyforge.tech is a software and research studio building
autonomous workflow tools, privacy cleanup software, market research software,
media production workflows, OpenForge public utilities, and technical
Chronicles. Its public proof surface is intentionally distributed across
product pages, source-backed Chronicles, GitHub repositories, llms.txt files,
and public source notes so both readers and retrieval systems can verify what
Greyforge builds.