{
  "schema_version": "1.0",
  "updated_at": "2026-09-04",
  "organization": {
    "id": "https://jumphash.com/#org",
    "name": "JUMPHASH",
    "url": "https://jumphash.com/",
    "description": "JUMPHASH builds and operates software and hardware systems, with a focus on reproducible behavior and reliable operation.",
    "contact_url": "https://jumphash.com/contact/",
    "email": "hello@jumphash.com",
    "logo": "https://jumphash.com/png/icon-512.png"
  },
  "services": [],
  "products": [
    {
      "id": "lorrano",
      "title": "Lorrano",
      "url": "https://jumphash.com/products/lorrano/",
      "description": "AI video generation for dealership inventory.",
      "status": "production",
      "external_url": "https://lorrano.com/",
      "updated_at": "2026-09-04"
    },
    {
      "id": "cargrid",
      "title": "Cargrid",
      "url": "https://jumphash.com/products/cargrid/",
      "description": "AI-search discoverability for dealerships.",
      "status": "production",
      "external_url": "https://cargrid.io/",
      "updated_at": "2026-09-04"
    },
    {
      "id": "mincut",
      "title": "Mincut",
      "url": "https://jumphash.com/products/mincut/",
      "description": "Verification-first electronics design: a tiered, reviewed parts registry, datasheet-grounded electrical checks, composable verified blocks, and fabrication packages. The project uses KiCad-native files.",
      "status": "development",
      "external_url": "https://mincut.dev/",
      "updated_at": "2026-09-04"
    },
    {
      "id": "provenira",
      "title": "Provenira",
      "url": "https://jumphash.com/products/provenira/",
      "description": "Infrastructure for proof of origin: Digital Product Passports, GS1 resolvers, and consumer product pages. The published scope covers the Western Balkans, Slovenia and German-speaking export markets, with Bosnian, Croatian, Slovenian, German and English content.",
      "status": "development",
      "external_url": "https://provenira.com/",
      "updated_at": "2026-09-04"
    },
    {
      "id": "beeldyard",
      "title": "Beeldyard",
      "url": "https://jumphash.com/products/beeldyard/",
      "description": "A browser-based building configurator for construction-materials merchants: select a structure, see it in 3D, and prepare a bill of materials priced against a merchant’s catalogue.",
      "status": "development",
      "external_url": "https://beeldyard.com/",
      "updated_at": "2026-09-04"
    },
    {
      "id": "parkyra",
      "title": "Parkyra",
      "url": "https://jumphash.com/products/parkyra/",
      "description": "Smart parking with a planned driver experience for reserving an exact space, navigating to it, and paying by cash, card or wallet, alongside an operator dashboard for parking, payments and devices.",
      "status": "development",
      "external_url": "https://parkyra.com/",
      "updated_at": "2026-09-04"
    },
    {
      "id": "contentopolis",
      "title": "Contentopolis",
      "url": "https://jumphash.com/products/contentopolis/",
      "description": "A content factory API: a brand kit and a brief are inputs for copy, images and rendered video. The published project scope includes a web app for agencies and a REST API for developers.",
      "status": "development",
      "external_url": "https://contentopolis.ai/",
      "updated_at": "2026-09-04"
    }
  ],
  "resources": [
    {
      "id": "about",
      "title": "About JUMPHASH",
      "url": "https://jumphash.com/about/",
      "description": "Understand JUMPHASH’s software and hardware portfolio, its focus on reproducible behavior, and where to find project information or contact the company.",
      "kind": "company",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/about.md",
      "content": "# About JUMPHASH\n\nUnderstand JUMPHASH’s software and hardware portfolio, its focus on reproducible behavior, and where to find project information or contact the company.\n\nSource: https://jumphash.com/about/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## Software, hardware and the systems around them\n\nJUMPHASH builds and operates software and hardware systems. Its public portfolio spans automotive AI, electronics design, product provenance, construction tooling, smart parking and content generation.\n\nThe engineering focus is reproducible behavior: make inputs and assumptions explicit, check expected outputs, and make failures understandable. A hash function can return an identical result for identical inputs; an AI product needs a different and more specific definition of reliable behavior.\n\n## What the portfolio tells you\n\nThe product directory identifies each system, its intended audience, its published lifecycle status and its own website. Development projects are clearly marked, so you can distinguish a project’s direction from an available product.\n\n## How we explain our engineering\n\nThe engineering notes explain decisions through concrete examples and their limitations. Our internal implementation studies show how those decisions appear in this website and its public information.\n\n- Credit source research and distinguish it from our implementation.\n- State the inputs, expected output and limits of an example.\n- Separate a source-code observation from a deployed performance result.\n\n## Talk to JUMPHASH\n\nFor a company, product or engineering inquiry, write to hello@jumphash.com or use the contact form. Include the system involved, the problem you want to solve and any relevant constraints. Specific scope and availability are agreed through that conversation.\n\n## Related\n\n- [Explore the portfolio](https://jumphash.com/products/)\n- [Read the engineering notes](https://jumphash.com/engineering/)\n- [Contact JUMPHASH](https://jumphash.com/contact/)\n",
      "source_urls": []
    },
    {
      "id": "product-lorrano",
      "title": "Lorrano in the JUMPHASH portfolio",
      "url": "https://jumphash.com/products/lorrano/",
      "description": "AI video generation for dealership inventory.",
      "kind": "product",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/product-lorrano.md",
      "content": "# Lorrano in the JUMPHASH portfolio\n\nAI video generation for dealership inventory.\n\nSource: https://jumphash.com/products/lorrano/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## What the project does\n\nAI video generation for dealership inventory.\n\n## Who it is for\n\nLorrano focuses on automotive · ai video for automotive dealerships.\n\nListed as production. Visit the product website for current features, access and pricing.\n\n## Relationship to JUMPHASH\n\nLorrano is part of the JUMPHASH portfolio of software and hardware systems. Explore the product at lorrano.com, or contact JUMPHASH with a question about the project.\n\n## Sources\n\n- [Lorrano — primary product website](https://lorrano.com/)\n\n## Related\n\n- [All JUMPHASH products](https://jumphash.com/products/)\n- [About JUMPHASH](https://jumphash.com/about/)\n- [Ask about this product](https://jumphash.com/contact/)\n",
      "source_urls": [
        "https://lorrano.com/"
      ]
    },
    {
      "id": "product-cargrid",
      "title": "Cargrid in the JUMPHASH portfolio",
      "url": "https://jumphash.com/products/cargrid/",
      "description": "AI-search discoverability for dealerships.",
      "kind": "product",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/product-cargrid.md",
      "content": "# Cargrid in the JUMPHASH portfolio\n\nAI-search discoverability for dealerships.\n\nSource: https://jumphash.com/products/cargrid/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## What the project does\n\nAI-search discoverability for dealerships.\n\n## Who it is for\n\nCargrid focuses on automotive · ai search for automotive dealerships.\n\nListed as production. Visit the product website for current features, access and pricing.\n\n## Relationship to JUMPHASH\n\nCargrid is part of the JUMPHASH portfolio of software and hardware systems. Explore the product at cargrid.io, or contact JUMPHASH with a question about the project.\n\n## Sources\n\n- [Cargrid — primary product website](https://cargrid.io/)\n\n## Related\n\n- [All JUMPHASH products](https://jumphash.com/products/)\n- [About JUMPHASH](https://jumphash.com/about/)\n- [Ask about this product](https://jumphash.com/contact/)\n",
      "source_urls": [
        "https://cargrid.io/"
      ]
    },
    {
      "id": "product-mincut",
      "title": "Mincut in the JUMPHASH portfolio",
      "url": "https://jumphash.com/products/mincut/",
      "description": "Verification-first electronics design: a tiered, reviewed parts registry, datasheet-grounded electrical checks, composable verified blocks, and fabrication packages. The project uses KiCad-native files.",
      "kind": "product",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/product-mincut.md",
      "content": "# Mincut in the JUMPHASH portfolio\n\nVerification-first electronics design: a tiered, reviewed parts registry, datasheet-grounded electrical checks, composable verified blocks, and fabrication packages. The project uses KiCad-native files.\n\nSource: https://jumphash.com/products/mincut/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## What the project does\n\nVerification-first electronics design: a tiered, reviewed parts registry, datasheet-grounded electrical checks, composable verified blocks, and fabrication packages. The project uses KiCad-native files.\n\n## Who it is for\n\nMincut focuses on eda · verification for electronics designers.\n\nIn development. The description outlines the project direction. Visit the product website for updates, or contact JUMPHASH to ask about access.\n\n## Relationship to JUMPHASH\n\nMincut is part of the JUMPHASH portfolio of software and hardware systems. Explore the product at mincut.dev, or contact JUMPHASH with a question about the project.\n\n## Sources\n\n- [Mincut — primary product website](https://mincut.dev/)\n\n## Related\n\n- [All JUMPHASH products](https://jumphash.com/products/)\n- [About JUMPHASH](https://jumphash.com/about/)\n- [Ask about this product](https://jumphash.com/contact/)\n",
      "source_urls": [
        "https://mincut.dev/"
      ]
    },
    {
      "id": "product-provenira",
      "title": "Provenira in the JUMPHASH portfolio",
      "url": "https://jumphash.com/products/provenira/",
      "description": "Infrastructure for proof of origin: Digital Product Passports, GS1 resolvers, and consumer product pages. The published scope covers the Western Balkans, Slovenia and German-speaking export markets, with Bosnian, Croatian, Slovenian, German and English content.",
      "kind": "product",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/product-provenira.md",
      "content": "# Provenira in the JUMPHASH portfolio\n\nInfrastructure for proof of origin: Digital Product Passports, GS1 resolvers, and consumer product pages. The published scope covers the Western Balkans, Slovenia and German-speaking export markets, with Bosnian, Croatian, Slovenian, German and English content.\n\nSource: https://jumphash.com/products/provenira/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## What the project does\n\nInfrastructure for proof of origin: Digital Product Passports, GS1 resolvers, and consumer product pages. The published scope covers the Western Balkans, Slovenia and German-speaking export markets, with Bosnian, Croatian, Slovenian, German and English content.\n\n## Who it is for\n\nProvenira focuses on provenance · product information for organizations publishing product provenance information.\n\nIn development. The description outlines the project direction. Visit the product website for updates, or contact JUMPHASH to ask about access.\n\n## Relationship to JUMPHASH\n\nProvenira is part of the JUMPHASH portfolio of software and hardware systems. Explore the product at provenira.com, or contact JUMPHASH with a question about the project.\n\n## Sources\n\n- [Provenira — primary product website](https://provenira.com/)\n\n## Related\n\n- [All JUMPHASH products](https://jumphash.com/products/)\n- [About JUMPHASH](https://jumphash.com/about/)\n- [Ask about this product](https://jumphash.com/contact/)\n",
      "source_urls": [
        "https://provenira.com/"
      ]
    },
    {
      "id": "product-beeldyard",
      "title": "Beeldyard in the JUMPHASH portfolio",
      "url": "https://jumphash.com/products/beeldyard/",
      "description": "A browser-based building configurator for construction-materials merchants: select a structure, see it in 3D, and prepare a bill of materials priced against a merchant’s catalogue.",
      "kind": "product",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/product-beeldyard.md",
      "content": "# Beeldyard in the JUMPHASH portfolio\n\nA browser-based building configurator for construction-materials merchants: select a structure, see it in 3D, and prepare a bill of materials priced against a merchant’s catalogue.\n\nSource: https://jumphash.com/products/beeldyard/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## What the project does\n\nA browser-based building configurator for construction-materials merchants: select a structure, see it in 3D, and prepare a bill of materials priced against a merchant’s catalogue.\n\n## Who it is for\n\nBeeldyard focuses on construction · 3d for construction-materials merchants.\n\nIn development. The description outlines the project direction. Visit the product website for updates, or contact JUMPHASH to ask about access.\n\n## Relationship to JUMPHASH\n\nBeeldyard is part of the JUMPHASH portfolio of software and hardware systems. Explore the product at beeldyard.com, or contact JUMPHASH with a question about the project.\n\n## Sources\n\n- [Beeldyard — primary product website](https://beeldyard.com/)\n\n## Related\n\n- [All JUMPHASH products](https://jumphash.com/products/)\n- [About JUMPHASH](https://jumphash.com/about/)\n- [Ask about this product](https://jumphash.com/contact/)\n",
      "source_urls": [
        "https://beeldyard.com/"
      ]
    },
    {
      "id": "product-parkyra",
      "title": "Parkyra in the JUMPHASH portfolio",
      "url": "https://jumphash.com/products/parkyra/",
      "description": "Smart parking with a planned driver experience for reserving an exact space, navigating to it, and paying by cash, card or wallet, alongside an operator dashboard for parking, payments and devices.",
      "kind": "product",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/product-parkyra.md",
      "content": "# Parkyra in the JUMPHASH portfolio\n\nSmart parking with a planned driver experience for reserving an exact space, navigating to it, and paying by cash, card or wallet, alongside an operator dashboard for parking, payments and devices.\n\nSource: https://jumphash.com/products/parkyra/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## What the project does\n\nSmart parking with a planned driver experience for reserving an exact space, navigating to it, and paying by cash, card or wallet, alongside an operator dashboard for parking, payments and devices.\n\n## Who it is for\n\nParkyra focuses on mobility · iot for parking operators and drivers.\n\nIn development. The description outlines the project direction. Visit the product website for updates, or contact JUMPHASH to ask about access.\n\n## Relationship to JUMPHASH\n\nParkyra is part of the JUMPHASH portfolio of software and hardware systems. Explore the product at parkyra.com, or contact JUMPHASH with a question about the project.\n\n## Sources\n\n- [Parkyra — primary product website](https://parkyra.com/)\n\n## Related\n\n- [All JUMPHASH products](https://jumphash.com/products/)\n- [About JUMPHASH](https://jumphash.com/about/)\n- [Ask about this product](https://jumphash.com/contact/)\n",
      "source_urls": [
        "https://parkyra.com/"
      ]
    },
    {
      "id": "product-contentopolis",
      "title": "Contentopolis in the JUMPHASH portfolio",
      "url": "https://jumphash.com/products/contentopolis/",
      "description": "A content factory API: a brand kit and a brief are inputs for copy, images and rendered video. The published project scope includes a web app for agencies and a REST API for developers.",
      "kind": "product",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/product-contentopolis.md",
      "content": "# Contentopolis in the JUMPHASH portfolio\n\nA content factory API: a brand kit and a brief are inputs for copy, images and rendered video. The published project scope includes a web app for agencies and a REST API for developers.\n\nSource: https://jumphash.com/products/contentopolis/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## What the project does\n\nA content factory API: a brand kit and a brief are inputs for copy, images and rendered video. The published project scope includes a web app for agencies and a REST API for developers.\n\n## Who it is for\n\nContentopolis focuses on ai · content for agencies and developers.\n\nIn development. The description outlines the project direction. Visit the product website for updates, or contact JUMPHASH to ask about access.\n\n## Relationship to JUMPHASH\n\nContentopolis is part of the JUMPHASH portfolio of software and hardware systems. Explore the product at contentopolis.ai, or contact JUMPHASH with a question about the project.\n\n## Sources\n\n- [Contentopolis — primary product website](https://contentopolis.ai/)\n\n## Related\n\n- [All JUMPHASH products](https://jumphash.com/products/)\n- [About JUMPHASH](https://jumphash.com/about/)\n- [Ask about this product](https://jumphash.com/contact/)\n",
      "source_urls": [
        "https://contentopolis.ai/"
      ]
    },
    {
      "id": "jump-consistent-hashing",
      "title": "Jump consistent hashing: from text to a repeatable bucket",
      "url": "https://jumphash.com/engineering/jump-consistent-hashing/",
      "description": "Follow the JUMPHASH demo from UTF-8 text through FNV-1a to a bucket, with exact examples and practical limits.",
      "kind": "engineering",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/jump-consistent-hashing.md",
      "content": "# Jump consistent hashing: from text to a repeatable bucket\n\nFollow the JUMPHASH demo from UTF-8 text through FNV-1a to a bucket, with exact examples and practical limits.\n\nSource: https://jumphash.com/engineering/jump-consistent-hashing/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## A small, testable promise\n\nThe homepage demonstration takes a text key and selects one of 96 numbered buckets. Entering the same text again produces the same bucket because the byte encoding, arithmetic and bucket count stay fixed. This is a narrow, observable example of determinism; it says nothing about the reliability of a network or the correctness of an entire application.\n\nJohn Lamping and Eric Veach introduced jump consistent hash in their 2014 paper. JUMPHASH is the company name; the algorithm is the authors’ work. Our demonstration combines a text hash with an integer implementation of their bucket-selection approach.\n\n## Keep the two steps separate\n\nFirst, TextEncoder turns the text into UTF-8 bytes. FNV-1a starts at the 64-bit offset basis, XORs each byte into the current value, multiplies by its prime and masks the result to 64 bits. Second, jumpHash takes that integer and the bucket count. It advances candidate bucket positions until the next candidate would be outside the range.\n\nThe implementation uses JavaScript BigInt for integer arithmetic. The mask makes the intended 64-bit wraparound explicit; integer division discards the fractional part. The bucket number is converted to Number only at the end.\n\n```javascript\nconst key = fnv1a64(\"jumphash\");\nhexOf(key);        // 0x7EC173F1A74C4759\njumpHash(key, 96); // 90\njumpHash(key, 1024); // 975\n```\n\n## Examples you can reproduce\n\nThe displayed bucket is zero-based: 90/96 means bucket 90 in the range 0 through 95. These examples are checks of our implementation, not a statistical benchmark.\n\n| Input text | Bucket count | Expected bucket |\n| --- | --- | --- |\n| jumphash | 96 | 90 |\n| jumphash | 1024 | 975 |\n| berza | 96 | 77 |\n| krov | 96 | 50 |\n\n## The interface also has a contract\n\nAn empty input in the homepage demo uses the example word jumphash. That is a user-interface choice, not a property of FNV-1a or jump consistent hash. The demo also limits entered text to 64 JavaScript string units and makes truncation visible.\n\nText that looks the same can have different Unicode encodings. This example does not normalize Unicode, change case or remove whitespace. Systems that need those transformations should define them before hashing and test the exact bytes that every consumer uses.\n\n## Where the guarantee stops\n\nThe original algorithm expects sequential bucket numbers. Arbitrarily removing a named server is a different membership problem; do not substitute a bucket-count change for a complete storage or routing design.\n\nFNV is non-cryptographic. Neither a bucket nor an FNV digest is an authentication token, a secret, a proof of identity or a privacy-preserving identifier. Different inputs can share a bucket, and digest collisions are possible. The demonstration does not test load balance, collision resistance, membership recovery or application throughput.\n\nBefore using this code elsewhere, validate positive integer bucket counts, define encoding and normalization, compare expected vectors across languages, and test the application’s actual membership changes. The homepage keeps its count fixed at 96.\n\n## Sources\n\n- [Lamping and Veach: A Fast, Minimal Memory, Consistent Hash Algorithm (2014)](https://arxiv.org/abs/1406.2294)\n- [RFC 9923: The FNV Non-Cryptographic Hash Algorithm](https://www.rfc-editor.org/rfc/rfc9923.html)\n\n## Related\n\n- [Try the homepage demonstration](https://jumphash.com/#demo)\n- [Internal study: a prerendered hash demonstration](https://jumphash.com/work/hash-demonstration/)\n",
      "source_urls": [
        "https://arxiv.org/abs/1406.2294",
        "https://www.rfc-editor.org/rfc/rfc9923.html"
      ]
    },
    {
      "id": "static-content-progressive-interaction",
      "title": "Static content, progressive interaction: choosing what needs JavaScript",
      "url": "https://jumphash.com/engineering/static-content-progressive-interaction/",
      "description": "How the JUMPHASH site separates readable content from interactive controls, and how to check its failure modes.",
      "kind": "engineering",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/static-content-progressive-interaction.md",
      "content": "# Static content, progressive interaction: choosing what needs JavaScript\n\nHow the JUMPHASH site separates readable content from interactive controls, and how to check its failure modes.\n\nSource: https://jumphash.com/engineering/static-content-progressive-interaction/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\n## Start with the information the visitor came for\n\nA company description, product status or engineering explanation should be available when its document arrives. On this site, Astro generates the page text, links and metadata as HTML during the build. Interactive controls enhance that document separately.\n\nAstro calls these independently hydrated components client islands. A component without a client directive can contribute rendered HTML without sending its component runtime to the browser. The decision belongs to each component, not to the page as a whole.\n\n## Assign behavior deliberately\n\nThe portfolio table only displays public records, so it renders without hydration. The hash demo needs to respond to typing, so it hydrates on page load. The homepage contact form becomes interactive when visible. Decorative background work waits for browser idle time. Article pages do not need that background.\n\n| Element | Needs browser behavior? | Reason |\n| --- | --- | --- |\n| Product text and links | No | Read and navigate using HTML |\n| Hash input | Yes | Recalculate when the key changes |\n| Contact form | Yes | Obtain a challenge and submit the inquiry |\n| Decorative canvas | Optional | Visual presentation only |\n\n## A failure between scripts still matters\n\nTesting with all JavaScript disabled is useful, but it misses partial failure. A head script might run while a later script fails. If the head script marks the page as JavaScript-enabled and CSS hides content until a later observer reveals it, the page can remain unreadable.\n\nThe revised content styling leaves essential text visible regardless of observer state. Reduced-motion preferences and a pause control stop decorative motion; background canvas work also stops when the document is hidden. These are behavior choices, not a claim that every device achieves a particular performance score.\n\n## Separate reading from successful submission\n\nA readable static form is not evidence that a message was delivered. Form submission requires a valid endpoint, a usable anti-abuse challenge and a durable server acknowledgment. A direct email link gives visitors another contact path when the interactive path is unavailable.\n\nThis distinction also applies to robots and assistants. Public documents can be read without invoking the contact API. Access to public company information is not permission to submit a message or read private inquiries.\n\n## Check the resulting experience\n\nInspect the generated HTML for the actual text, links, canonical URL and metadata. Then try normal JavaScript, no JavaScript, failed hydration, keyboard navigation and reduced motion. On representative pages, record measured LCP, INP and CLS rather than inferring them from the framework choice.\n\nThis article describes this site’s implementation and a verification method. It does not report a field-performance improvement, a search-ranking gain or a conversion experiment. Those require measurements from the deployed version and an appropriate observation period.\n\n## Sources\n\n- [Astro: islands architecture](https://docs.astro.build/en/concepts/islands/)\n\n## Related\n\n- [Internal study: one source for public product information](https://jumphash.com/work/public-information-pipeline/)\n- [Explore the product directory](https://jumphash.com/products/)\n",
      "source_urls": [
        "https://docs.astro.build/en/concepts/islands/"
      ]
    },
    {
      "id": "hash-demonstration",
      "title": "Internal implementation study: a prerendered hash demonstration",
      "url": "https://jumphash.com/work/hash-demonstration/",
      "description": "How the JUMPHASH homepage renders a repeatable hash result before hydration, with the boundaries of the example made explicit.",
      "kind": "internal-study",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/hash-demonstration.md",
      "content": "# Internal implementation study: a prerendered hash demonstration\n\nHow the JUMPHASH homepage renders a repeatable hash result before hydration, with the boundaries of the example made explicit.\n\nSource: https://jumphash.com/work/hash-demonstration/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\nInternal JUMPHASH implementation study. No customer outcome or endorsement is claimed.\n\n## Context and responsibility\n\nThe subject of this internal study is the homepage hash demonstration on JUMPHASH’s own website.\n\nThe design goal is to let a visitor see one concrete deterministic calculation and then try another input. The initial result needs to be readable before the component becomes interactive.\n\n## Implementation\n\nThe React component starts with an empty field and substitutes jumphash as its example key. The shared FNV-1a function derives a 64-bit integer, and jumpHash selects a bucket with a fixed count of 96. Astro renders that initial result into the page; hydration connects the input events.\n\nThe same module provides the expected-vector checks. Keeping the displayed result and the checks on the same encoding and arithmetic avoids documenting a different calculation from the one the visitor sees.\n\n- UTF-8 encoding is explicit through TextEncoder.\n- BigInt and a 64-bit mask define integer behavior.\n- The range is labeled from bucket 00 through 95.\n- The input explains truncation when the demonstration limit is reached.\n\n## Observable result\n\nFor jumphash, the expected digest is 0x7EC173F1A74C4759 and the result is bucket 90 at a count of 96. At 1,024 buckets the expected result is 975. The engineering note includes further examples and the original research attribution.\n\nThese are deterministic example outputs. They do not establish collision resistance, cluster availability, balanced production traffic or a measured business result.\n\n## Limits and reuse\n\nThe demo fixes its bucket count and treats an empty field as an example. A production consumer must define its own input normalization, membership model, valid bucket-count range and error behavior. It must also verify the entire consumer path rather than assuming that passing a small demonstration proves the system correct.\n\n## Sources\n\n- [Original jump consistent hash research](https://arxiv.org/abs/1406.2294)\n\n## Related\n\n- [Read the algorithm walkthrough](https://jumphash.com/engineering/jump-consistent-hashing/)\n- [Try the demonstration](https://jumphash.com/#demo)\n",
      "source_urls": [
        "https://arxiv.org/abs/1406.2294"
      ]
    },
    {
      "id": "public-information-pipeline",
      "title": "Internal implementation study: one source for public product information",
      "url": "https://jumphash.com/work/public-information-pipeline/",
      "description": "How shared typed records keep JUMPHASH’s HTML directory, product pages and machine-readable catalog aligned.",
      "kind": "internal-study",
      "published_at": "2026-09-04",
      "updated_at": "2026-09-04",
      "markdown_url": "https://jumphash.com/content/public-information-pipeline.md",
      "content": "# Internal implementation study: one source for public product information\n\nHow shared typed records keep JUMPHASH’s HTML directory, product pages and machine-readable catalog aligned.\n\nSource: https://jumphash.com/work/public-information-pipeline/\nContent owner: JUMPHASH\nUpdated: 2026-09-04\n\nInternal JUMPHASH implementation study. No customer outcome or endorsement is claimed.\n\n## Context and responsibility\n\nThis internal study covers the JUMPHASH website’s public content implementation.\n\nThe site presents a portfolio overview, individual product descriptions and public machine-readable documents. Independently editing the same lifecycle status in every format creates avoidable disagreement.\n\n## A shared record, several presentations\n\nEach product record contains a stable ID, name, description, audience, domain, published lifecycle status and primary product URL. The homepage table, portfolio cards and individual product pages read those records. The public JSON catalog and Markdown documents derive from the same records.\n\nAuthored resources use structured sections, tables, related links and source citations. HTML and Markdown render those sections independently without maintaining a second editorial copy.\n\n- Canonical page URLs point to the company’s public HTML documents.\n- External product URLs identify the primary product websites.\n- A content update date records an editorial change, not a new product launch.\n\n## Boundaries of the catalog\n\nThe catalog contains public company, product and editorial information. It does not contain contact submissions, subscriber information, credentials or administrative records. It is a retrieval format; it does not grant permission to perform an action.\n\nA listed development product remains a development product in each format. A content format should preserve the meaning and scope of the source record, not add claims that its renderer cannot substantiate.\n\n## What this implementation can establish\n\nRendered-output checks can compare IDs, descriptions, statuses, canonical URLs and links across the generated formats. They can catch missing files and disagreement between templates. They cannot prove that a company fact is true; the owner still needs to review the underlying record.\n\nThere is no measured traffic, citation or conversion uplift in this study. Those results require deployed observations. The immediate engineering outcome is a defined public-content boundary and a single editorial source for repeated facts.\n\n## Related\n\n- [Read the public catalog](https://jumphash.com/catalog.json)\n- [Static content and progressive interaction](https://jumphash.com/engineering/static-content-progressive-interaction/)\n- [Explore the products](https://jumphash.com/products/)\n",
      "source_urls": []
    }
  ]
}