RSRitik Sharma
Research / PublicationsOnline

Research

All publications2

  1. Ritik Sharmarcp-standard.md

    Created 6 Nov 2026

    A benchmark proposal for delivered performance and system capability

    • 1 file
    • 238 lines
    • 3,726 words

    Ritik Compute Power (RCP) Standard

    A benchmark proposal for delivered performance and system capability

    Ritik Sharma · Version 1.0 proposal · 6 November 2026

    Publication status · Technical preprint and proposed specification. This document includes formal analysis and synthetic verification cases. The executable Core suite, reference measurements, and cross-platform validation are pending.

    Abstract

    A computing system can excel at a small workload, fail to fit a larger one, and deliver different throughput after reaching thermal equilibrium. Peak operation rates and composite benchmark scores answer narrower questions than this combination of performance and feasibility. Ritik Compute Power (RCP) proposes a two-part result. A dimensionless Core score summarizes verified end-to-end performance on a versioned workload profile. A mandatory capability signature reports raw results, feasible workload sizes under declared constraints, sustained behavior, energy, and failure reasons. The proposed Balanced profile assigns fixed weights to twelve workload categories. This paper defines eligibility, normalization, aggregation, and reporting, proves the score's principal mathematical properties, and gives a protocol for evaluating the method on heterogeneous systems. Comparability is defined by a shared workload contract and a declared system boundary.

    The RCP Core equation

    RCP(M)=100∏i=1nri(M)wi=100exp⁡ ⁣(∑i=1nwiln⁡ri(M))\boxed{\mathrm{RCP}(M) = 100 \prod_{i=1}^{n} r_i(M)^{w_i} = 100 \exp\!\left(\sum_{i=1}^{n} w_i \ln r_i(M)\right)}

  2. Ritik Sharmaritik-wiki.md

    Created 9 Apr 2026

    A pattern for building persistent personal knowledge bases with LLMs.

    • 1 file
    • 323 lines
    • 1,717 words

    Ritik Wiki

    A pattern for building persistent personal knowledge bases with LLMs.

    This is an idea file. It is meant to be copied into your LLM agent of choice (for example Codex, Claude Code, OpenCode, or similar) so the agent can help you build and maintain the system with you.

    The purpose of this document is not to prescribe one exact implementation. Its purpose is to communicate the pattern clearly enough that an LLM can turn it into a working setup adapted to your domain, workflow, and tooling.

    The core idea

    Most document workflows with LLMs are basically retrieval systems.

    You upload documents, the LLM retrieves relevant chunks at question time, and then generates an answer. This is useful, but it has a major limitation: the knowledge is reassembled from scratch every time. The model keeps rediscovering the same facts, the same relationships, and the same contradictions over and over again.