[Submission] Tactors SDK - Typed actors on top of temporal

[youaresofunny]

Project link

https://github.com/tactors/sdk

Language

Go

Short description (max 256 chars)

Typed, builder-first actor SDK for Go built on Temporal.io: describe stateful workflows, commands, queries, and activities with fluent APIs, then run them deterministically across Temporal workers and testsuite scenarios.

Long Description

Tactors SDK

Tactors is a typed, builder-first actor SDK for Go. You describe state, handlers, activities, and
runtime knobs in one fluent API and receive a deterministic actor description that every runtime can
consume—no code generation or interface{} plumbing.

What you get

• Typed actor builders: fix state with actors.NewStateful, get typed commands/queries/activities
  via helper embeds, and build once for every runtime consumer.
• Declarative knobs: retries, timeouts, caches, queue overrides, snapshots, and validators live on
  the builder so intent is obvious.
• Temporal-first runtime: one actors.Description powers worker registration, Ask/Query plumbing,
  and the deterministic testsuite—no alt runtimes or codegen.
• Ops hooks: spans/metrics around commands and cross-actor calls; rotation/versioning via
  WithSnapshot and actors.Patch.

Author(s)

https://github.com/youaresofunny

[github-actions]

Hi, I'm ZiggyBot! 🤖 Here's my pre-evaluation of this submission:

---

Criterion	Assessment
Useful to Temporal users	✅ Yes — Provides a typed, builder-pattern abstraction over Temporal's workflow/activity primitives that reduces boilerplate and eliminates interface{} plumbing for Go developers building actor-style systems.
Benefits clearly explained	✅ Yes — The README clearly articulates the value proposition (typed builders, declarative configuration, testsuite integration) and provides a comprehensive docs map for deeper exploration.
OSI Approved License	✅ Yes — Released under the MIT License, which is OSI-approved and community-friendly.
README with working instructions	✅ Yes — Includes a quick start guide, test command, and links to detailed documentation and a separate samples repository with runnable examples.

Overall: Looks good ✅

Notes:

• This is a thoughtful abstraction layer that brings actor-model semantics to Temporal while preserving type safety—a real pain point for Go developers working with Temporal's signal/query patterns.
• The project demonstrates good architectural discipline: separate repos for SDK and samples, comprehensive documentation structure, and a testkit that integrates with Temporal's native testsuite.
• The low star count (3) suggests it's early-stage, but the code quality and documentation maturity indicate serious intent.
• The control/schedule.go file shows nice use of search attributes for durable interval scheduling that survives Continue-As-New—a pattern many Temporal users struggle with.

Suggested questions for submitter:

• Could you share any production usage or performance characteristics compared to raw Temporal SDK usage?
• The docs mention "cross-namespace" routing—could you elaborate on the use cases this enables?

Teaching moment:

The control/schedule.go file demonstrates a clever pattern for persisting schedule state across Continue-As-New boundaries using search attributes. Instead of losing interval timing when a workflow continues, it stores the next run timestamp in a search attribute (__actors_control_schedule.<name>) and recovers it on restart. This is a practical solution to a common challenge: maintaining durable timers in long-running workflows that need history rotation.
View in source ↗

---

ZiggyBot is an AI pre-screener based on Temporal's community mascot Ziggy. Final decisions are made by the community team.

[Shy]

Thanks for participating in the hackathon. If you're happy with where this project ended and are open with us sharing it, let us know and we'll get it up on code exchange for other folks to learn from?

[youaresofunny]

Thanks for participating in the hackathon. If you're happy with where this project ended and are open with us sharing it, let us know and we'll get it up on code exchange for other folks to learn from?

Yes, i'm happy with where this project ended, feel free to open it up!)

[Shy]

Posted. Thanks for contributing!