July Allspice updates: Hierarchy & DRCY enhancements

July was all about you! We've been heads-down turning your feedback into meaningful improvements, from smarter, more repeatable reviews to a clearer look at your schematic hierarchy and richer API documentation. Here's what's new.

📝 View all product updates in detail on our Headway changelog. Updated every other week.

July Allspice updates lead image showing a DRCY AI comment on a schematic, with feature tags for schematic hierarchy, DRCY review resume, py-allspice API examples, and @DRCY comments.
Written by:
Nick Herbert
|
Updated on:
November 11, 2026

🏛️  See your schematic hierarchy, not just a flat list

Your schematic sheets, as they were meant to be viewed

Design Reviews used to show every schematic sheet in one flat list, even when your design was built from parent and child sheets. Now it displays that hierarchy, so you can see which sheets nest under which, the way you already do in your ECAD tool. Support is live for Cadence De-HDL, Cadence System Capture, and Cadence OrCAD to start, with the rest on the way.

Allspice design review file tree showing nested parent and child schematic sheets under top_module.dsn, next to previews of each sheet.

→Read the full update here

‍

📍 Pick up where DRCY left off with review resume

Automatically down-select to unreviewed pages

If DRCY runs out of time and posts a partial review, you can now resume with just a few clicks; open the “Request DRCY” menu and click “Resume” to automatically uncheck the reviewed pages so you can quickly kick off DRCY on the remainder of the design.

Request DRCY menu in Allspice with a prompt to resume a partial review and a checklist of schematic pages to review: Fans, Microcontroller, Power, and USB.

→Read the full update here

‍

💬 Give DRCY feedback with @DRCY comments

Improve a review, correct a mistake, or add new context

Inject critical design context by adding a comment to the Design Review, starting with “@DRCY”. You can tell DRCY about your design patterns, such as using attributes for DNP, or system context such as a connected-device. You can respond to a DRCY comment to correct a component misunderstanding or describe operational logic.

Design review comment addressed to @DRCY explaining how component U36 enables turbo mode based on the barrel jack power source.

→Read the full update here

‍

🧩 New examples in our API documentation

Moving forward you can see specific examples for the core and relevant endpoints within our API wrapper (py-allspice) to understand its usage and implementation. You can see them by going to an endpoint doc like Allspice API and then selecting py-allspice in the example box on the right.

→Read the full update here

‍

That’s it for this month’s product updates. We’re excited to keep making hardware development faster and easier, and we appreciate everyone who shares feedback along the way. Questions, feature requests, or demo requests are always welcome!

‍

Valentina Ratner, Co-Founder & CEO of AllSpice
Nick Herbert
Senior Product Manager

I bring an engineer-first mindset to product development, grounded in real design constraints, tight timelines, and the realities of shipping hardware.
As a Senior Product Manager at Allspice, I work closely with hardware teams and customers to improve how engineers collaborate, review designs, and catch issues earlier in development.
Before Allspice, I spent a decade at EPAM Continuum building and leading electronics programs across a range of complex products. That mix of hands-on hardware development, systems thinking, and consulting gives me a practical view of where design reviews break down and how teams can fix them.