# `gno.land/p/nym-moultest123/entity`

> 🚧 **API sketch, not an implementation.** The interfaces below are declared;
> all three constructors `panic("not implemented")`. Nothing here works yet.

A proposal for one type that stands for "whoever is acting", whether that is an
externally owned account or a realm.

```go
type Entity interface {
	Addr() address
	Path() string    // "" for an EOA, the pkgpath for a realm
	Kind
	isEntity()
}
```

`UserEntity` and `RealmEntity` narrow it, and `Kind` is meant to carry the
second axis: a user can be a person or a team, a realm can be an arbitrary
contract or one that implements a known interface such as a DAO.

```go
func NewUserByAddr(addr address) UserEntity    // panics today
func NewUserByName(name string) UserEntity     // panics today
func NewRealm(rlm runtime.Realm) RealmEntity   // panics today
```

The motivation is that gno code constantly branches on "is this an address or a
pkgpath", and that branch leaks into every API that wants to accept either. A
single `Entity` would let a realm accept both and let composition (an entity
that matches several others) be expressed once.

Closely related to [`p/moul/ownable`](../ownable), which is the same idea
narrowed to ownership.

<!-- BEGIN GNOCONTRACTS FOOTER (generated by `make readmes`; do not edit below) -->

---

Part of **[moul/gno-contracts](https://github.com/moul/gno-contracts)** — moul's versioned gno.land contracts. See the repository for the full catalog, build/test tooling, and usage.

> ⚠️ **Disclaimer:** provided as-is, without warranty; not security-audited. Full disclaimer: [DISCLAIMER](https://github.com/moul/gno-contracts/blob/main/DISCLAIMER.md).

<!-- END GNOCONTRACTS FOOTER -->