AP1S3 (human, Q96PC3) — curation notes

σ1C / sigma-3, one of three interchangeable small subunits of the heterotetrameric AP-1
clathrin adaptor. 154 aa, no catalytic machinery, a single longin/roadblock fold. The gene is
best known clinically as a pustular-psoriasis susceptibility locus (PSORS15), and that
literature dominates a Europe PMC search on the symbol — but the cell-biological substance of
the gene is now carried by two high-resolution structures in which AP1S3 itself is the
crystallised or imaged chain, and both were missed by the affinage record.

Accession check: AP1S3-uniprot.txt is ID AP1S3_HUMAN, AC Q96PC3; — the expected protein,
not a merged redirect. Entry version 178, 2026-09-02.

1. What the gene product is

AP-1 is a cytosolic heterotetramer that coats trans-Golgi-network and endosomal membranes
PMID:24791904. Its four chains are two large
adaptins (γ/AP1G1, β1/AP1B1), a medium adaptin (μ1/AP1M1 or AP1M2) and one small adaptin —
and UniProt states plainly that the small slot is filled by any of three gene products
[file:human/AP1S3/AP1S3-uniprot.txt "(sigma-type subunit AP1S1 or AP1S2 or AP1S3)."]. So
AP1S3 is not a distinct complex, it is one of three variants of the same complex. The
ComplexPortal makes that explicit as a named object,
[file:human/AP1S3/AP1S3-uniprot.txt "DR ComplexPortal; CPX-5049; Ubiquitous AP-1 Adaptor complex, sigma1c variant."],
whose declared composition is AP1B1:AP1G1:AP1M1:AP1S3.

Family placement: PANTHER PTHR11753 ADAPTOR COMPLEXES SMALL SUBUNIT FAMILY. The reviewed-entry
index interpro/panther/PTHR11753/PTHR11753-entries.csv lists seven human members —
AP2S1, AP1S2, AP3S2, AP1S1, AP3S1, AP1S3, AP4S1. AP5S1 is not in that index, so the family
should not be described as spanning AP1–AP5 on the basis of this slice.

2. The two structures that actually contain AP1S3

This is the part of the record that neither the affinage report nor GOA currently reflects.

PDB 7R4H — 2.34 Å cryo-EM, ARF1-activated AP-1 core bound to TBK1-phosphorylated STING
(PMID:36261523). The recombinant complex is
PMID:36261523
— σ 1–154, and 154 aa is AP1S3's full length. PDBe SIFTS maps chain S of 7R4H to Q96PC3
residues 1–154. The structure shows the σ subunit reading a classical acidic dileucine sorting
motif:
PMID:36261523,
with an added phospho-readout
PMID:36261523.

PDB 9DDT — 1.68 Å X-ray, AAGAB pseudoGTPase domain bound to AP1S3 (PMID:40752490). Here
the construct is named outright: "Full-length human AP1S3 (Uniprot Q96PC3–1)", and
PMID:40752490.
The interface is large and specific
PMID:40752490, and crucially it is the
same surface
as the cargo site:
PMID:40752490
and
PMID:40752490.
AAGAB is the assembly chaperone
PMID:40752490
and it is what makes a σ subunit fold at all
PMID:40752490.

So the σ subunit of AP-1 has a real, subunit-level biochemical job: it supplies the
hydrophobic pockets that read the [DE]XXXL[LI] sorting signal in a cargo tail, and that same
pocket is capped by the chaperone until the tetramer is built. That is a far more informative
statement than the protein binding and protein targeting rows GOA currently carries.

Bioinformatics check (see AP1S3-bioinformatics/RESULTS.md)

Because both papers describe "the σ subunit" by residue number only, I tested whether the
numbering is AP1S3's. sigma_site_check.py fetches Q96PC3/P61966/P56377/P53680 live, asserts
their lengths, and resolves 23 published positions.

A caveat this analysis surfaced, and which changes what can be annotated. The cellular
mutagenesis in PMID:36261523 (σKR K60A/R61A, σ V88D, σ I103S abolishing STING–AP-1 binding)
was not done on AP1S3:
PMID:36261523
— the plasmid is pCDNA3-HA-AP1S1. Because V88 and I103 are the same residue at the same
position in both paralogues, the result bears on the shared σ site, but it is loss-of-function
data on AP1S1. AP1S3's own evidence in that paper is structural (chain S of 7R4H). I therefore
do not propose a STING/type-I-interferon process row for AP1S3; the loss-of-function
subunit in that paper's cell work is AP1S1, and siAP1S3 appears only in its reagent list.

3. Loss-of-function phenotypes that are AP1S3's own

TLR3 delivery to endosomes (PMID:24791904). Three knockdown lines, in two backgrounds, and
it is worth keeping straight which result came from which. The two stable shRNA lines are
keratinocytes —
PMID:24791904
— and they carry both the trafficking readout
PMID:24791904
and the interferon readout
PMID:24791904.
A third, separately generated knockdown line is HEK293 —
PMID:24791904
— and it reproduces the trafficking defect but not (because it was not measured there) the
interferon one:
PMID:24791904.
So the localisation defect is not keratinocyte-restricted, while the IFNB1 result is a
keratinocyte measurement. This is knockdown evidence — IMP-grade, not IDA — and GOA codes it
IMP, correctly. The readout is specifically where TLR3 ends up, which is why
protein targeting (GO:0006605) is under-informative for it and protein localization to endosome (GO:0036010) is the right grain.

Autophagosome formation (PMID:27388993). Two independent perturbations plus a rescue:
PMID:27388993
in HaCaT, confirmed in a CRISPR knockout —
PMID:27388993
— and, decisively for direction,
PMID:27388993.
The mechanistic premise is complex-level
PMID:27388993, i.e.
AP1S3 acts through AP-1-dependent membrane traffic rather than as autophagy machinery. Note
the knockout was made in HEK293, not a keratinocyte, so the autophagy requirement is not
keratinocyte-restricted; only the inflammatory consequence (p62 → NF-κB → IL-36α) was
studied in keratinocytes. This is the basis for proposing GO:0000045 as a NEW row.

Disease variants. p.Phe4Cys destabilises the protein
PMID:24791904;
p.Arg33Trp acts on assembly, not on cargo —
PMID:24791904. Both sit outside
the cargo surface mapped in 7R4H/9DDT, consistent with loss of functional complex rather than
altered cargo selectivity.

Virus host factor (PMID:27079945, abstract only): AP1S3 silencing in Huh7.5.1 cells
reduces HCV progeny, and AP1S3 co-immunoprecipitates HCV E2, protecting it from proteasomal
degradation. Real but a host-factor role for a viral protein, not a native function; not
proposed for annotation.

Cancer association studies (PMID:34367317 glioma, PMID:40555003 breast cancer): TCGA
expression correlations plus knockdown proliferation/migration assays. Too far downstream of a
housekeeping trafficking adaptor to support a process annotation.

4. Expression — the "restricted expression" premise does not hold

UniProt says [file:human/AP1S3/AP1S3-uniprot.txt "CC -!- TISSUE SPECIFICITY: Widely expressed."],
Bgee reports expression in an islet of Langerhans "and 106 other cell types or tissues", and
HPA calls it [file:human/AP1S3/AP1S3-uniprot.txt "DR HPA; ENSG00000152056; Tissue enhanced (epididymis)."]
— enhanced, not restricted. The only quantitative comparison in the primary literature is
PMID:27388993's survey of disease-relevant cells
PMID:27388993,
which is a statement about three haematopoietic/epithelial populations, not a tissue atlas.
Nothing in the record warrants down-grading the TGN/endosome location rows on expression
grounds: the compartment claims are about where the protein acts when present, and AP1S3 is
present broadly.

5. The single IBA, traced

GOA carries exactly one IBA: GO:0016192 vesicle-mediated transport, involved_in,
GO_REF:0000033, dated 20250902, with WITH/FROM
CGD:CAL0000182525|FB:FBgn0039132|FB:FBgn0043012|MGI:MGI:1098244|MGI:MGI:1889383|PANTHER:PTN000204281|PomBase:SPAP27G11.06c|RGD:620188|SGD:S000003561|SGD:S000004160|UniProtKB:P53680|WB:WBGene00000157
— the node plus eleven gene-level donors.

interpro/panther/PTHR11753/PTHR11753-paint.tsv contains the family's whole PAINT slice: two
IBD rows, both on PTN000204281 — GO:0016192 (P) and GO:0043231 (C). The GO:0016192 IBD
row (refreshed 20260828) lists ten seeds; the 2025 IBA WITH/FROM carries the same ten plus
FB:FBgn0043012, which is a seed of the other IBD row on the same node. The difference is a
snapshot-date artefact, not a defect. No IRD or IKR row exists anywhere in this family's slice.

Donor resolution (UniProt xref lookups, ≥2 hits requested; QuickGO for each donor's own
annotations under GO:0016192 and descendants):

WITH/FROM resolves to own evidence under GO:0016192
CGD:CAL0000182525 Q59QC5 APS3, C. albicans AP-3 σ GO:0006896 IMP (PMID:20870878)
FB:FBgn0039132 AP-1σ (CG5864), D. melanogaster, TrEMBL only IEA/ISS only — no experimental
FB:FBgn0043012 Q9VDC3 AP-2σ (CG6056), D. melanogaster GO:0035615 IMP (PMID:20226669); GO:0016192 NAS
MGI:MGI:1098244 P61967 Ap1s1 mouse GO:0042147 IMP (PMID:24928897)
MGI:MGI:1889383 Q9DB50 Ap1s2 mouse GO:0016192 IMP (PMID:24928897); GO:0016182, GO:0036465 IDA/IMP
PomBase:SPAP27G11.06c Q9P7N2 aps1/vas2 S. pombe GO:0042147, GO:0099638 IDA (PMID:19624755)
RGD:620188 P62744 Ap2s1 rat GO:0098884 EXP/IDA/IMP (PMID:17289840)
SGD:S000003561 P47064 APS3 S. cerevisiae GO:0006896 IMP (PMID:9335339)
SGD:S000004160 P35181 APS1 S. cerevisiae GO:0006896 IMP (PMID:17003107)
UniProtKB:P53680 AP2S1 human GO:0048488 IDA/IMP (PMID:11102472); GO:0072583 TAS
WB:WBGene00000157 Q19123 aps-2 C. elegans GO:0072583 IMP (PMID:25303366)

Ten of eleven donors carry experimental evidence, but they carry it in different descendant
branches
— Golgi-to-vacuole transport, endosome-to-Golgi transport, clathrin-dependent
endocytosis, synaptic vesicle endocytosis, postsynaptic receptor internalisation. That is
precisely the situation in which the parent vesicle-mediated transport is the correct least
common ancestor, and it is why this IBA is not a granularity failure: a more specific child
would have to pick one compartment and would be wrong for the rest of the clade. Root cause
NO_FAILURE_CORE.

AP1S3 is not among its own donors — it has no experimental GO:0016192 of its own — so this is
not a self-referential IBA. AP1S3 sits squarely inside the clade: PANTHER classifies it into
PTHR11753 with no subfamily assignment, and it retains the entire σ fold and, per §2, the
functional cargo site.

One loose end worth recording rather than asserting: the same node carries an IBD for
GO:0043231 intracellular membrane-bounded organelle, but no corresponding IBA appears in
AP1S3's GOA. I do not know whether that reflects the GOA snapshot date (the IBA is 20250902,
the IBD row 20260528) or a GOA filter on very general CC terms, and I have not asserted
either.

6. Where the remaining 44 rows come from

The ARBA rule, checked rather than waved through

ARBA00033972 confers exactly one annotation, GO:0032588, through ten unrelated condition
sets (EF-hand, protein-kinase, ARM-repeat and other FunFams, each with its own taxon
restriction). The set that fires for AP1S3 is CS9: FunFam 3.30.450.60:FF:000005 +
taxon Catarrhini
— and 3.30.450.60:FF:000005 is precisely the FunFam UniProt assigns to
this entry ("FunFam; 3.30.450.60:FF:000005; AP complex subunit sigma"). The matching condition
set is therefore σ-specific, not an accidental fold match, and the conferred location is one
UniProt and Reactome both assert independently. Accepted.

7. Curation decisions, and why

Counts, produced by .scratch/reconcile.py rather than typed: 45 GOA rows reconcile one-for-one
with 45 reviewed YAML entries (identical term/evidence/reference/supporting_entities); actions
are ACCEPT 37, KEEP_AS_NON_CORE 5, MODIFY 3, NEW 2; 12 rows carry a propagation_review (1 IBA,
10 IEA, and the IC NEW row whose basis term is recorded machine-readably) and every
source_entities list matches its row's supporting_entities exactly; 36 references, all with a
reference_review; 162 supporting_text quotes, all verified by checkquotes.py; 8
residue_claims, 24 checks, 0 failures.

8. What affinage missed, and what it got right

The record's frontmatter is clean (self_evaluation_pairwise: win, faith_pct: 100.0) and
.affinage.log reports "AP1S3: trust gates clear", so no gate tripped. Its six citations are all numeric PMIDs, all
real, and its narrative correctly identifies σ1C, TLR3 trafficking, autophagy/p62/IL-36 and
the HCV E2 interaction. It also honestly flags that PMID:27411398 characterises σ1A and σ1B
and not σ1C — and indeed that paper does not contain the string "AP1S3" at all.

What it missed is the entire structural literature: PMID:36261523 (cited by UniProt as
reference [6] of this very entry, with FUNCTION and SUBUNIT evidence) and PMID:40752490
(the 2025 paper whose crystallised protein is AP1S3). Both are titled for the partner —
"Clathrin-associated AP-1 controls termination of STING signalling" and "Structural basis of
pseudoGTPase-mediated protein-protein interactions" — which is the documented affinage failure
mode: precision, not recall. Neither surfaces on a naive AP1S3 Europe PMC search either;
36261523 was found by reading the UniProt reference list, and 40752490 by searching the PDB
accession 9DDT that UniProt's DR lines carry. Its mechanism_profile grounding
(GO:0060090 molecular adaptor activity, GO:0005768 endosome) was not imported; the
grounding here is re-derived from UniProt, the structures and the GO definitions.

Also absent from affinage: PMID:18428203, which supplies the redundancy framing that makes
sense of AP1S3's mild, tissue-limited phenotype —
PMID:18428203 (σ1A, σ1B, σ1C) — and the
statement that σ subunits are essential for AP-complex stability. Abstract-only in our cache.

9. Open questions

  1. Is there any cargo that the σ1C form of AP-1 selects and the σ1A/σ1B forms do not? Nothing
    in the record addresses this, and it is the question that would decide whether AP1S3
    deserves its own process annotations at all rather than inheriting the complex's.
  2. Why is the phenotype epidermal if the gene is widely expressed and the complex redundant?
    The candidate answer in the literature is relative abundance in keratinocytes plus the IL-36
    amplification loop, but no isoform-swap experiment has been done.
  3. Which AP-1 σ variant handles STING? 7R4H used AP1S3; the cellular knockdowns and mutants in
    the same paper used AP1S1. These may be interchangeable, but it has not been tested.
  4. Four isoforms are annotated, two of them NMD candidates, and the MANE-Select transcript
    encodes isoform 4 (C-terminus TMEEYMNKPTF) while the UniProt canonical is isoform 1
    (VSTVSQTMGER). Both structures used isoform 1. Nothing is known about isoform-specific
    function, and no GO annotation is isoform-qualified.