PrajnaEdge is not navigated like a conventional website. Knowledge is represented through paths, structures, and transitions.
Matter
NodeClick a node name to enter that concept and continue along the awakened path.
ExplorationsStep-by-step learning experiences containing theory, architecture, and interactive elements.
SetuA Setu connects related concepts that can be explored independently from the main sequence.
VortexA Vortex opens a path toward another knowledge area, foundation, or future domain.
BlackholeA deeper exploration space opened through the Vortex, where you select the depth of investigation.
AntarguhaA concealed exploration existing outside the regular path, waiting to be discovered within the system.
For the best experience, open PrajnaEdge on a desktop or laptop screen.
PrajnaEdge
A curiosphere for curious minds who want to understand, experiment with, and experience technology.
Technology is a system of connections.
Modern technology is built from layers that continuously interact with one another. At the physical level, electronic devices transform electrical signals into digital information. Digital logic turns that information into computation, while processors, memory and communication interfaces provide the machinery needed to execute instructions and move data. As these components become part of embedded systems, they begin to interact with the physical world through sensors, controllers, actuators and real-time software.
But computation does not exist in isolation. Operating systems coordinate hardware and software, firmware gives specialized machines their behaviour, and communication protocols allow independent systems to exchange information. At the same time, machine learning is moving beyond the cloud into edge and on-device systems, where models must operate within real constraints such as memory, processing power, latency and energy consumption.
PrajnaEdge explores these connections as one continuous technology landscape — and takes them beyond explanation. From computing foundations and embedded systems to intelligent machines and edge AI, ideas can be understood, experimented with, and eventually turned into technology that can be experienced in the real world.
PrajnaEdge products and technology experiences are currently in development.
In Development
Playground
Experiment with intelligence beyond the cloud.
AI runs closer to where data is generated — reducing dependence on distant cloud infrastructure and enabling faster, more responsive systems.
Edge AIComputer Vision
Image Classification
Can this image classifier maintain its intelligence while becoming small enough for the edge?
On-Device AIComing later
On-Device Intelligence
AI runs directly on the device where data is generated, bringing intelligence into the device itself while operating within its compute, memory, power and latency constraints.
Edge AI Playground
Image Classification
Can this image classifier maintain its intelligence while becoming small enough for the edge?
Choose an image
Upload an image
Supports JPG, JPEG, PNG
This classifier recognizes only Apple, Banana, and Orange. Other objects may be incorrectly classified as one of these classes.
AI runs directly on the device where data is generated, bringing intelligence into the device itself while operating within its compute, memory, power and latency constraints.
Coming later
Explorations
Explore the ideas, systems and connections that shape technology — choose any node to begin your journey.
Embedded Systems Tree
Sort by:
Edge AI Demonstrations
Deploying neural networks and intelligent decision loops on raw silicon targets.
Sort:
Operating Systems
The Name Is Not the File
Understanding directories, path resolution, and filesystem identity.
When we interact with persistent storage, we locate and open files using names:
notes.txt
To a user or a programmer, it is natural to assume that the name is the file itself.
But this assumption is incorrect.
A filename is merely a string used to identify an object. It is not the underlying file object, nor is it the physical container of the data. A filename is a name used for lookup within a namespace. The physical data blocks on disk and the metadata describing them have an entirely separate identity.
This separation becomes more apparent when we construct a sequence of names to identify a file—a Path:
/home/dev/projects/notes.txt
A path is not a single physical string stored on disk that points directly to a sector. Instead, a path is a map. It represents a route that the operating system must navigate component by component to find the target object.
2. From Path to File
To resolve the path /home/dev/projects/notes.txt, the filesystem must step through each component of the directory hierarchy:
The process begins at the absolute root of the filesystem namespace. The operating system looks up the root node, retrieves its contents, finds the mapping for home, and traverses downward. It repeats this matching step for dev and projects until it gets the entry for notes.txt.
A path is not a pointer to data. A path is a set of instructions for navigating a hierarchical namespace.
3. Directories Are Not Folders
In graphical user interfaces, directories are styled as "folders"—visual bins that contain physical files.
Conceptually, however, a directory is a mapping table. It is an organizational structure that translates human-readable name strings into unique filesystem internal identities.
A directory provides mappings from names to filesystem objects. When we look up notes.txt inside a directory table, we receive the internal index key. By nesting directory objects inside other directory tables, the filesystem builds the entire hierarchical directory tree.
4. EdgeCase: Path Resolution
Watch the interactive sequence below to trace how the operating system resolves /home/dev/projects/notes.txt from the root node through nested directories, retrieving directory entry tables along the path:
5. The Surprising Part: Name ≠ Identity
Because directories only link names to identities, the name of a file is decoupled from the file itself. This means multiple names can point to the same underlying file identity.
This relationship is known as a Hard Link:
In this system, both report.txt and backup.txt entries are registered inside a directory pointing to the exact same file metadata entry (Inode #7182).
This is not a copy. Both names refer to the exact same file. If a program writes to report.txt and updates its content, a subsequent read of backup.txt immediately reveals those updates. The file remains alive until all names pointing to its inode reference are deleted (reducing the link count to 0).
6. Symbolic Links
Another way to map names is through a Symbolic Link (often called a symlink or shortcut).
Unlike a hard link, which points directly to the file identity, a symbolic link is a separate file that stores a path string referencing another name:
The difference between the two configurations is fundamental:
* Hard Link: A direct path from multiple names to the same target inode.
* Symbolic Link: A path from a name to a new file object whose data payload contains the text string of another path.
If the target name report.txt is deleted, the symlink latest.txt remains behind but becomes a "broken link," resolving to a path that no longer exists.
7. Relative vs. Absolute Paths
Paths can be specified in two formats:
* Absolute: Starts from the root token (/), e.g., /home/dev/projects/notes.txt. Resolution always begins at root.
* Relative: Does not start from root, e.g., projects/notes.txt. Resolution begins from a contextual environment—typically the process's Current Working Directory (CWD).
This context means the same relative path can resolve to different physical files depending on which folder the application is executed from.
8. Real Operating-System Connection
While disk format structures vary across operating systems, the core programming interface remains uniform.
For instance, Linux filesystems (like ext4) implement directory entries as tables mapping name strings to numerical index nodes (inodes). The inode contains all metadata and block addresses, but has no knowledge of the name itself. Regardless of the underlying operating system—be it Windows, macOS, or Linux—the OS presents the exact same unified namespace abstraction (names, paths, directories, and file objects) to user application processes.
9. The Next Question
How does the filesystem keep track of all this information — the file's metadata, its directory entries, its data blocks, and the free space around them?
Engineering concepts you don't just read — you experience.
Founded in 2026.
PrajnaEdge is a technology company exploring the space between understanding technology, experimenting with ideas, and turning them into things that can be experienced.
Our Mission
To make technology easier to explore, deeper to understand, and more exciting to experience.
Our Vision
To build a technology ecosystem where curiosity, experimentation and creation continuously lead to one another.
Where it began
Embedded Systems
PrajnaEdge began with Embedded Systems — exploring the foundations that connect hardware, software and intelligent computation.
The first technology universe is built around that foundation. The journey will expand as new ideas, experiments and products emerge.
I am the engineer behind the design, development, and content of PrajnaEdge. I build low-level systems where code directly controls hardware, bridging the gap between register-level silicon behavior and intelligent edge decision loops.
I am an Embedded Firmware Engineer focused on developing software for resource-constrained systems. My experience spans bare-metal firmware, device drivers, microcontroller peripherals, and communication protocols, working across the boundary between hardware and software.
My work has involved microcontroller-based systems, real-time behaviour, hardware interfaces, and communication technologies such as CAN, CAN FD, UART, SPI, and I²C. I am particularly interested in understanding systems from the lowest level upward—from registers and peripherals to intelligent edge systems.
ENGINEERING PHILOSOPHY
Engineering is not just about writing code; it is about managing constraints, timings, and physical hardware characteristics. True mastery of complex systems comes from understanding the interactions across different layers of the stack.
This conviction is why I built PrajnaEdge—to bridge the gap between conceptual theory and direct, register-level physical reality.
Where it all began — understanding the physical layer of computation. Circuits, signals, and systems gave me a mental model of how information moves through hardware.
⬡
Connects to Systems Understanding circuits directly enables writing firmware that talks to peripherals at the register level.
What it is
BTech in Electronics and Communication
Undergraduate foundation covering analog & digital circuits, signal processing, microprocessors, and communication systems.
CircuitsSignal ProcessingMicroprocessorsVLSI
What I did
Core Engineering Fundamentals
Studied semiconductor physics, digital logic design, and embedded microcontrollers. Built prototypes using 8-bit MCUs.
8051Logic DesignPCB Basics
What I learned
The Hardware Mental Model
Every software abstraction sits on physical reality. Understanding silicon teaches you why timing, power, and noise are first-class engineering problems.
Let's Connect
Interested in embedded systems, AI, or building something meaningful? I'd love to hear from you.
PrajnaEdge is an independent education platform built to make knowledge freely accessible.
If you find PrajnaEdge useful, you can support its continued development.
Your support helps fund the time, tools, infrastructure, and experimentation that go into building and maintaining PrajnaEdge.
Select Region
Select Amount
₹
Select an amount to support PrajnaEdge.
Legal & Privacy
Last updated: September 2026
1. Terms of Use
Welcome to PrajnaEdge (prajnaedge.dev), an independent engineering and technology platform created and maintained by Devaharsha Meesarapu. By using this website, you agree to these terms.
Educational & Research Focus: PrajnaEdge publishes interactive technical explorations, architectural models, and simulation walk-throughs covering embedded systems, computer architecture, operating systems, and edge artificial intelligence. All materials, interactive tools, and code demonstrations are provided solely for educational and conceptual understanding.
Hardware & Firmware Disclaimer: Embedded programming interacts directly with hardware registers, physical voltages, and precise timing. While all writeups and code demonstrations are prepared with care, they are provided "as is" without warranty of any kind. You are responsible for reviewing component datasheets, circuit schematics, and electrical ratings before deploying code to physical microcontrollers or custom hardware.
PrajnaEdge is committed to user privacy and minimal data collection. We do not sell, rent, or monetize your personal information.
Voluntary Correspondence: When you submit a message through the Contact or Feedback forms, or write directly to contact@prajnaedge.dev, we receive your name, email address, and message. This information is used strictly to reply to your inquiry.
Server Diagnostics: Standard web hosting infrastructure automatically logs basic technical access data (such as IP address, browser type, and timestamps) for server security, performance monitoring, and error diagnostics.
Local Storage: PrajnaEdge uses client-side browser localStorage purely to remember your interface preferences on your device (such as sound preferences for animations and tutorial display states). No personal identity data is stored in localStorage.
3. Advertising & Cookies
To help support platform operation and hosting, PrajnaEdge displays advertisements served by third-party advertising partners, including Google AdSense.
Advertising Cookies: Google and other third-party vendors use cookies to serve ads based on your prior visits to this website and other websites across the Internet.
DoubleClick / DART Cookie: Google's use of advertising cookies enables it and its partners to serve ads based on your visit to PrajnaEdge and other sites on the web.
Third-Party Ad Networks: When advertisements are requested by your browser, third-party ad networks automatically receive your IP address and may use technologies such as cookies or web beacons to measure ad effectiveness. PrajnaEdge does not control these cookies set by third-party advertisers.
4. Analytics
We use Google Analytics (measurement tag: G-6Y8ZVQB1V0) to evaluate anonymous, aggregate usage trends across our technical writeups.
Aggregate Telemetry: Google Analytics uses cookies to collect anonymous metrics such as page visit counts, device screen sizes, and navigation flows. This data helps us optimize responsive layouts and focus on high-interest topics.
Voluntary Support (Razorpay): If you choose to support PrajnaEdge through the Support page, transactions are handled through Razorpay's PCI-DSS compliant checkout interface. PrajnaEdge never handles, collects, or stores payment card numbers, UPI PINs, or banking credentials.
5. User Rights & Contact
Depending on your jurisdiction (including rights under GDPR, CCPA/CPRA, and applicable privacy laws), you have the right to request access to, correction of, or deletion of any personal communications you have submitted. We do not sell personal data.
For any questions regarding these terms, privacy practices, or data inquiries, contact the creator directly:
